Jira (PUP-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File"
Title: Message Title Joshua Cooper commented on an issue Re: Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" Glad to hear the issue was resolved Stefan Lasiewski, I'll go ahead and close this ticket. Add Comment Puppet / PUP-2345 Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" I am running a Scientific Linux 6.x system with Foreman and Puppet 3.4. Yesterday I ran `yum update`. Afterwards, Puppet failed. Downgrading Puppet from 3.5 to 3.4 prevents the error, and is what I am doing for a workaround. Steps to reproduce: 1. Notice that the error doesn't happen with Puppet 3.4 [root@puppetmaster ~]# puppet --version 3 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.googl
Jira (PUP-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File"
Title: Message Title Stefan Lasiewski commented on an issue Re: Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" Thanks for the tip. It looks like Ruby gems did install the 'puppet' and 'puppet-lint' gems. I uninstalled both of those using `gem uninstall puppet` and now the error goes away. ``` gem list LOCAL GEMS *** ansi (1.4.3) awesome_print (1.2.0, 1.0.2) clamp (0.6.3, 0.6.2) daemon_controller (1.2.0, 1.1.5) facter (1.7.5) fastercsv (1.5.5, 1.5.4) fastthread (1.0.7) foreman_api (0.1.11) gettext (2.1.0) hammer_cli (0.0.18) hashie (2.0.5) hiera (1.3.2) highline (1.6.21, 1.6.20) json (1.5.5) json_pure (1.8.1) kafo (0.5.2, 0.4.0, 0.3.17) kafo_parsers (0.0.2, 0.0.1) little-plugger (1.1.3) locale (2.0.5) logging (1.8.2, 1.8.1) mime-types (1.16) multi_json (1.9.2, 1.8.2) oauth (0.4.7) passenger (4.0.40, 4.0.5) powerbar (1.0.11) puppet (3.4.3) puppet-lint (0.3.2) rack (1.5.2, 1.1.0) rack-protection (1.5.2) rack-test (0.6.2, 0.5.4) rake (10.1.1, 0.8.7) rdoc (4.1.1, 3.12) rest-client (1.6.7, 1.6.1) rgen (0.6.6) rkerberos (0.1.2) rubyipmi (0.7.0) sinatra (1.4.4, 1.0) table_print (1.5.1, 1.1.5) tilt (1.4.1) # Add Comment Puppet / PUP-2345 Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Pupp
Jira (PUP-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File"
Title: Message Title Rob Reynolds commented on an issue Re: Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" So possible that having multiple installations of puppet is messing with the loadpath and causing this error. Add Comment Puppet / PUP-2345 Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" I am running a Scientific Linux 6.x system with Foreman and Puppet 3.4. Yesterday I ran `yum update`. Afterwards, Puppet failed. Downgrading Puppet from 3.5 to 3.4 prevents the error, and is what I am doing for a workaround. Steps to reproduce: 1. Notice that the error doesn't happen with Puppet 3.4 [root@puppetmaster ~]# puppet --version 3 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at h
Jira (PUP-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File"
Title: Message Title Richard Davies commented on an issue Re: Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" I had the same issue upgrading from 3.4.3 to 3.5.1 using the puppetlabs rpms on CentOS 6.5. For me it was caused by a puppet-3.4.3 gem installed outside of yum/rpm (as a dependency of puppet-lint or puppet-cleaner) found by: yum update ... ---> Package puppet.noarch 0:3.4.3-1.el6 will be updated ---> Package puppet.noarch 0:3.5.1-1.el6 will be an update ---> Package puppet-server.noarch 0:3.4.3-1.el6 will be updated ---> Package puppet-server.noarch 0:3.5.1-1.el6 will be an update ... Updated: puppet.noarch 0:3.5.1-1.el6 puppet-server.noarch 0:3.5.1-1.el6 Complete! puppet apply --no-daemonize --trace /etc/puppet/manifests/site.pp Notice: Compiled catalog for in environment production in 0.08 seconds Failed to load feature test for libuser: uninitialized constant Puppet::FileSystem::File Error: /File[/etc/puppet]: Could not evaluate: uninitialized constant Puppet::FileSystem::File /usr/lib/ruby/gems/1.8/gems/puppet-3.4.3/lib/puppet/type/file.rb:698:in `stat' /usr/lib/ruby/site_ruby/1.8/puppet/type/file/ensure.rb:166:in `retrieve' ... Updating that gem solved the problem for me, but it might be more reliable to remove it if it isn't needed. Add Comment Puppet / PUP-2345 Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File"
Jira (PUP-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File"
Title: Message Title Stefan Lasiewski commented on an issue Re: Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" I'm not sure, but this might be a duplicate of PUP-1603 : https://tickets.puppetlabs.com/browse/PUP-1603 Add Comment Puppet / PUP-2345 Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" I am running a Scientific Linux 6.x system with Foreman and Puppet 3.4. Yesterday I ran `yum update`. Afterwards, Puppet failed. Downgrading Puppet from 3.5 to 3.4 prevents the error, and is what I am doing for a workaround. Steps to reproduce: 1. Notice that the error doesn't happen with Puppet 3.4 [root@puppetmaster ~]# puppet --version 3 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-b
