Uploaded image for project: 'Puppet Agent'
  1. Puppet Agent
  2. PA-475

Puppet Agent 1.6.0 refuses to load custom gem

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: puppet-agent 1.6.0
    • Fix Version/s: puppet-agent 1.6.1
    • Component/s: Packaging, Windows
    • Labels:
      None
    • Environment:

      Windows 2012r2, Puppet Agent 1.6.0, tiny_tds 0.7.0

    • Template:
    • Sub-team:
    • Story Points:
      2
    • Sprint:
      RE Platforms 2016-08-17, RE Platforms 2016-08-24

      Description

      In previous Puppet Agent versions, 1.0 through 1.5 we were able to `gem install tiny_tds` and leverage it through custom puppet types, in Puppet Agent 1.6 this gem fails to load with a LoadError that can't load the library which is present.

      The stacktrace is:

      Exception `LoadError' at c:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/tiny_tds-0.7.0-x64-mingw32/lib/tiny_tds/2.1/tiny_tds.so - 126: The specified module could not be found.  - c:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/tiny_tds-0.7.0-x64-mingw32/lib/tiny_tds/2.1/tiny_tds.so
      Exception `LoadError' at c:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:133 - 126: The specified module could not be found.  - c:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/tiny_tds-0.7.0-x64-mingw32/lib/tiny_tds/2.1/tiny_tds.so
      

      and it just devolves from there. Not sure what changed in ruby library loading between 1.5 and 1.6. This worked perfectly in 1.5 before we received the 1.6 update last week.

        Attachments

          Activity

            People

            • Assignee:
              sean.mcdonald Sean McDonald
              Reporter:
              ruckc Curtis Ruck
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support