Closed brownandsticky closed 11 years ago
@brownandsticky these errors indicate that the module isn't able to autoload all of the custom ruby plugin information for this package. I suspect that this should be fixed in Puppet 3.1 and greater; are you able to test that version of Puppet and see if this issue resolves itself?
Alternately this error might indicate that the autoloader needs to be updated to scan for libraries in puppet/util
, but that's me musing more than anything else.
@adrienthebo I installed puppet-3.1.1-r1 and the issue is resolved. Many thanks.
I'm just starting down the Puppet road. But this module brings Gentoo's packaging peculiarities under Puppet control perfectly. It creates/updates "/etc/portage/package.*/default" with the USE flags, keywords etc specified in the manifest.
Change the file /usr/lib/ruby/site_ruby/1.8/puppet/util/autoload.rb to modify the load_file procedure to this form:
def load_file(name, env)
file = get_file(name.to_s, env)
return false unless file
begin
mark_loaded(name, file)
Kernel.load file, @wrap
return true
rescue SystemExit,NoMemoryError
raise
rescue Exception => detail2
begin
mark_loaded(name, file)
Kernel.load file, @wrap
return true
rescue Exception => detail
message = "Could not autoload #{name}: #{detail}"
Puppet.log_exception(detail, message)
raise Puppet::Error, message, detail.backtrace
end
end
end
The Kernel.load is not loading the file fast enough.
I got the same error using puppet 4.0.0, i downgraded to version 3.7.4 and everything is fine again.
Trying to get started with Puppet, but want to be sure Gentoo package.* are handled before embarking too far.
Fresh install of Gentoo and Puppet. Once the module is installed Puppet will complete no commands, returning: Could not run: Could not autoload /etc/puppet/modules/portage/lib/puppet/type/package_keywords.rb: cannot load such file -- puppet/util/portage
I've tried having portage.* as directories and files, revdep-rebuild, etc.
There was a closed issue on a very similar issue, but the solution the guy used still eludes me.
'hopefully the info below will be of use and it's a simple config error on my part. The Ruby warnings could be significant but again are beyond my ken.
<< snip >>