Jira (PUP-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File"

[Rob Reynolds (JIRA)]

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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.