Report processor failed: uninitialized constant Puppet::FileSystem::File

[ro001]

Hi,

I am the deploying the puppet master rpm 3.4.2 onto a centos 6.3 VM using the following script files but output reports the error 'Report processor failed: uninitialized constant Puppet::FileSystem::File', has anyone seen this error? 

****** SITE.pp ***********

import "nodetypes/*.pp"

Exec { path => "/bin:/sbin:/usr/bin:/usr/sbin" }

node 'TEST-PM4.com'

{

class {'puppetmaster' : }

}

node default {

}

# Filebuckets

filebucket { main: server => puppet }

filebucket { local: path => "/var/lib/puppet/clientbucket" }

class main {

}

******** puppet master manifest ********

class puppetmaster {

class { 'my-puppetmaster' : }

}

******* my-puppetmaster module *******

class my-puppetmaster {

$packages = [ 'puppet-server'

             ]

package { $packages:

    ensure => installed,

}

}

When I create the puppetmaster, the output finished with an error (as highlighted below). Has anyone else seen this Error? I have not spotted any problems from it, but it would be great if someone could share what the problem is?

[ro...@TEST-PM4.com puppet]# puppet apply manifests/site.pp

Notice: Compiled catalog for TEST-PM4.com in environment production in 1.00 seconds

Notice: /Stage[main]/my-puppetmaster/Package[puppet-server]/ensure: created

Notice: Finished catalog run in 5.35 seconds

Error: Report processor failed: uninitialized constant Puppet::FileSystem::File

[Felix Frank]

Hi,

apparently puppet cannot load the Puppet::FileSystem::File
class from $RUBYLIB/puppet/file_system/file.rb

Have you installed puppet via rpm package? Can you verify the
consistency of your installation?

Failing that, locate the above mentioned file in your file system and
find out why it's not used (correctly) or what's wrong with it. This may
be a red herring, though.

HTH,
Felix

[Mike Skint]

yes I've seen it on ubuntu 12.04 and Debian 6 nodes installed from puppetlabs repo,  had to roll back to 3.4.0

[Josh Cooper]

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/9de2db92-667c-4ad8-94cb-fe0336f489d1%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Can you run with --trace and attach the backtrace to a ticket (https://tickets.puppetlabs.com)?

Josh

--

Josh Cooper

Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14

Register now and save 40%! Offer expires January 31st.

[Luke Chavers]

I'm running into this as well.  While it seems to be a rare error, Google returns at least a few incidents of people with similar problems.  Since I doubt that this is a desired behavior, I'll call it a bug from this point.

I hit this bug when trying to install "The Foreman" via their official Puppet module.  Unless I'm wrong (and very well could be), all of the other mentions of this bug are similar in the sense that they all install a puppet server.

The OP here is installing a Puppet Master, I'm installing a Puppet Master (via Foreman), and it seems like another example I saw also included a Puppet Master, though I am unable to locate it now.

Notice: /Stage[main]/Foreman::Install::Repos::Extra/Yumrepo[SCL]/gpgkey: gpgkey changed '' to 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-Testing-6'

Notice: /Stage[main]/Puppet::Server::Install/Package[puppet-server]/ensure: created

Error: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml]: Failed to generate additional resources using 'eval_generate: uninitialized constant Puppet::FileSystem

Notice: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml]/ensure: created

Error: Could not back up /etc/sysconfig/ntpdate: uninitialized constant Puppet::FileSystem

There's also a ticket open in PuppetLabs JIRA, here: https://tickets.puppetlabs.com/browse/PUP-1603

Thanks,

Luke

[jcbollinger]

That is a pretty questionable manifest in that it may demand that Puppet update itself while it is running.  At least Puppet's 'apply' face must be installed already, because you need to use it to apply the manifests presented (I presume one would not do it via the agent, though the same problem would apply in that case, too).  Now suppose that either the current Puppet install was not performed via an OS package -- maybe it was a gem install, or even a source install -- or that the installed package is a lower version than the latest available "puppet-server" package.

In that case, installing the "puppet-server" package likely demands that a matching "puppet", "puppet-agent", etc. package be installed as well, replacing the then-running code right underneath Puppet.  That wouldn't necessarily be a big deal for a binary program that was already loaded into memory, but for Ruby (or Python or Perl ...) code, where some parts may not yet have been loaded, that's a problem waiting to happen.

Moreover, it's a problem that might be tricky to reproduce, inasmuch as whether it manifests probably depends on details of the target system's initial state, details of the manifests being applied, and details of the packages available.


John