Issue #17713 has been updated by Jeff McCune. Status changed from Accepted to Merged - Pending Release Target version set to 3.2.0
Merged into master as b3af03c. This should be released in 3.2.0. Thanks again for the contribution! -Jeff ---------------------------------------- Bug #17713: upstart service provider throws "warning: class variable access from toplevel" https://projects.puppetlabs.com/issues/17713#change-81125 Author: Andrew Regner Status: Merged - Pending Release Priority: Normal Assignee: Category: agent Target version: 3.2.0 Affected Puppet version: 3.0.1 Keywords: Branch: running `puppet agent --test` on my puppetmaster causes this warning to appear a bunch of times, even when no changes are happening: <pre> root@app1:~# puppet agent --test Info: Retrieving plugin Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Info: Caching catalog for app1 Info: Applying configuration version '1353302633' /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel /usr/local/rvm/gems/ruby-1.9.3-p194/gems/puppet-3.0.1/lib/puppet/provider/service/upstart.rb:67: warning: class variable access from toplevel Finished catalog run in 5.86 seconds </pre> As you can see I am using Ruby 1.9.3 and Puppet 3.0.1. This is all on Ubuntu 11.10, but ruby is compiled from source ala RVM and puppet is from "gem install". This doesn't seem to be causing any problems that I can see, but it is annoying. My other nodes are all stock-ruby and puppet 2.7 packages from the puppetlabs repo. They don't throw this warning. My puppetmaster never threw this warning either before I upgraded it to 3.0.1. (I upgraded to ruby 1.9.3 at the same time, for the record.) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
