Hi all, I''ve just started testing 2.7.8 after the release today, and almost immediately hit a problem: err: Could not create resources for managing Puppet''s files and directories in sections [:main, :agent, :ssl]: uninitialized constant Module::Win32API This occurs on multiple machines, under both "puppet agent" and "puppet master". Master is Debian Wheezy, clients are Archlinux. Last line of the trace seems to point the finger here: /usr/local/lib/site_ruby/1.8/puppet/util/adsi.rb:30:in `computer_name'' I''ve had a quick poke about in the requires but I can;t work out why two different OSes are trying to execute Windows code.... any pointers? Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/2ivDJd7hp4YJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Greg, On Fri, Dec 9, 2011 at 2:23 PM, Greg Sutcliffe <greg.sutcliffe@gmail.com>wrote:> Hi all, > > I''ve just started testing 2.7.8 after the release today, and almost > immediately hit a problem: > > err: Could not create resources for managing Puppet''s files and > directories in sections [:main, :agent, :ssl]: uninitialized constant > Module::Win32API > > This occurs on multiple machines, under both "puppet agent" and "puppet > master". Master is Debian Wheezy, clients are Archlinux. > > Last line of the trace seems to point the finger here: > > /usr/local/lib/site_ruby/1.8/puppet/util/adsi.rb:30:in `computer_name'' > > I''ve had a quick poke about in the requires but I can;t work out why two > different OSes are trying to execute Windows code.... any pointers? >It''s definitely running code that it shouldn''t. Can you run with `puppet agent --trace --debug` and post the backtrace? Thanks, Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Josh, Of course. I''ll pastie so as not to spam the list :) Here''s an Arch client - http://pastie.org/2993397 Here''s the Debian running "puppet master -- trace --debug" - http://pastie.org/2993401 Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/CLQ7bWd9wbAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Greg, On Fri, Dec 9, 2011 at 2:34 PM, Greg Sutcliffe <greg.sutcliffe@gmail.com>wrote:> > Here''s an Arch client - http://pastie.org/2993397 > Here''s the Debian running "puppet master -- trace --debug" - > http://pastie.org/2993401 > >Thanks, puppet thinks it is running on both windows and posix simultaneously, amazing! Can you pastie the output of facter from the agent? And the output from: ruby -e "require ''rbconfig''; puts Config::CONFIG.inspect" Thanks, Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Josh, I''ll give you both in case it matters (since one is ruby 1.8 and one is 1.9) Master - http://pastie.org/2993476 Agent - http://pastie.org/2993486 I''m on IRC in #puppet (gwmngilfen) at the moment if you want to real-time the troubleshooting. Not a problem if you''ve got other priorities :) Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/FGFXVfWuIngJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Josh, I think I''ve found it. I fired up a spare (clean) Debian VM for testing - and no errors. So I poked further... A while back, I was plagued by this on my arch clients: Could not load confine test ''operatingsystem'': cannot load such file -- puppet/provider/confine/operatingsystem Intrigued why it was only on Arch, I copied operatingsystem.rb from another system into lib/puppet/provider/confine in one of my modules. When I removed it, 2.7.8 started working fine - on both OSes. So that''s the initial panic over... Any idea on a proper fix for the new (old? :P) issue? Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/5XnrfVI9BK0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Greg, On Fri, Dec 9, 2011 at 3:27 PM, Greg Sutcliffe <greg.sutcliffe@gmail.com>wrote:> Hi Josh, > > I think I''ve found it. I fired up a spare (clean) Debian VM for testing - > and no errors. So I poked further... > > A while back, I was plagued by this on my arch clients: > > Could not load confine test ''operatingsystem'': cannot load such file -- > puppet/provider/confine/operatingsystem >Normally this message only occurs when a provider is confined, and the confine exists, but puppet fails to load it. However, it appears that ruby 1.9.3 changes the error message associated with the LoadError when calling require on a file that doesn''t exist. And this causes puppet to not suppress the warning, which is actually benign in this case. I''ve filed this as https://projects.puppetlabs.com/issues/11325>Intrigued why it was only on Arch, I copied operatingsystem.rb from another> system into lib/puppet/provider/confine in one of my modules. >This caused puppet to to think the windows providers were suitable instead of relying on the operatingsystem fact to make that determination.> When I removed it, 2.7.8 started working fine - on both OSes. So that''s > the initial panic over... > >Great to hear! Note that we really only support 1.9.2 at this time, though we will certainly address any 1.9.3 issues that come up. Thanks, Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Josh, Thanks for clearing that up - given that it''s benign, then I won''t worry too much about it :) I''m pretty much stuck with whatever Arch decide to give me for Ruby versions. I guess that makes us Arch users the canary testers for Puppet. So far nothing seems broken - every message I get is only a warning. Are PuppetLabs interested in reports on what 1.9.3 errors I come across, or do you have your own roadmap for future ruby versions? I don''t want to open a bunch of tickets if they''ll be closed because of unsupported ruby versions - that''ll just annoy everyone involved :) Cheers again, Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/648iPhGyshYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.