Hi Greg, On Fri, Dec 9, 2011 at 3:27 PM, Greg Sutcliffe <[email protected]>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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
