Ask Your Question

Revision history [back]

Could not autoload... is caused by the proxy machine not being able to find the plugin. Most likely the easiest way to fix this is to put the f5 module in the environment of the proxy machine and do something to cause it to pluginsync the f5 plugins.

The issue is that the requires in the type only check the pluginsync directory of the proxy machine and don't check in the lib/ directory of the module. This can be solved with relative requires such as https://github.com/puppetlabs/puppetlabs-apt/blob/8649fb4aa67fb05c7b133ba98041f55e9fa22577/lib/puppet/provider/aptkey/aptkey.rb#L8 however the F5 types were not written this way.

Could not autoload... is caused by the proxy machine master not being able to find the plugin. Most likely the easiest way to fix this is to put the f5 module in the environment of the proxy machine master and do something to cause it to pluginsync the f5 plugins.plugins. Perhaps a daemon restart would be needed, but probably not.

The issue is that the requires in the type only check the pluginsync directory of the proxy machine master and don't check in the lib/ directory of the module. This can be solved with relative requires such as https://github.com/puppetlabs/puppetlabs-apt/blob/8649fb4aa67fb05c7b133ba98041f55e9fa22577/lib/puppet/provider/aptkey/aptkey.rb#L8 however the F5 types were not written this way.

Also, puppet should be fixed to be able to load code from the environment's modules' lib/ directories, but there is no bug for this and it has edge cases for when libraries from two modules have the same names...

Could not autoload... is caused by the master not being able to find the plugin. Most likely the easiest way to fix this is to put the f5 module in the environment of the master and do something to cause it to pluginsync the f5 plugins. Perhaps a daemon restart would be needed, but probably not.

The issue is that the requires in the type only check the pluginsync directory of the master and don't check in the lib/ directory of the module. This can be solved with relative requires such as https://github.com/puppetlabs/puppetlabs-apt/blob/8649fb4aa67fb05c7b133ba98041f55e9fa22577/lib/puppet/provider/aptkey/aptkey.rb#L8 however the F5 types were not written this way.

Also, puppet should be fixed to be able to load code from the environment's modules' lib/ directories, but there is no bug for this and it has edge cases for when libraries from two modules have the same names...

Could not autoload... is caused by the master not being able to find the plugin. Most likely the easiest way to fix this is to put the f5 module in the environment of the master and do something to cause it to pluginsync the f5 plugins. Perhaps a daemon restart would be needed, but probably not.

The issue is that the requires in the type only check the pluginsync directory of the master and don't check in the lib/ directory of the module. This can be solved with relative requires such as https://github.com/puppetlabs/puppetlabs-apt/blob/8649fb4aa67fb05c7b133ba98041f55e9fa22577/lib/puppet/provider/aptkey/aptkey.rb#L8 https://github.com/puppetlabs/puppetlabs-apt/blob/8649fb4aa67fb05c7b133ba98041f55e9fa22577/lib/puppet/provider/apt_key/apt_key.rb#L8 however the F5 types were not written this way.

Also, puppet should be fixed to be able to load code from the environment's modules' lib/ directories, but there is no bug for this and it has edge cases for when libraries from two modules have the same names...