Issue #20573 has been updated by David Gordon.

Hi, so my master's puppet.conf has:
  manifest    = $confdir/environments/$environment/manifests/site.pp
  modulepath  = $confdir/environments/$environment/modules:/etc/puppet/modules

So, assuming $confdir is /etc/puppet:

I have symlinks, e.g. /etc/puppet/environments/app_a -> /some_share/app_a.

This allows applications to own/control their own modules by keeping them in 
/some_share/app_a and specifying --environment=app_a when they do runs.  These 
are application-user runs, not root...


----------------------------------------
Bug #20573: Sporadic "Error 400 on SERVER: Could not find class xxx for node 
[node] on [node]" problems
https://projects.puppetlabs.com/issues/20573#change-90722

* Author: David Gordon
* Status: Needs More Information
* Priority: Normal
* Assignee: David Gordon
* Category: 
* Target version: 
* Affected Puppet version: 
* Keywords: 
* Branch: 
----------------------------------------
Using the following Puppet packages:
  puppetdb-1.2.0-1.el6.noarch
  puppet-3.2.0-0.1rc1.el6.noarch
  puppet-dashboard-1.2.23-1.el6.noarch
  puppetdb-terminus-1.2.0-1.el6.noarch
  puppet-server-3.2.0-0.1rc1.el6.noarch

..with Ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
..on RHEL 2.6.32-220.13.1.el6.x86_64 

Dashboard-based ENC.  Puppetmaster running as a service.

If I initiate 2 puppets runs together via MCollective on 2 nodes, identical 
catalogues, one node can fail with "Error 400 on SERVER: Could not find class 
xxx for node [node] on [node]".  The error is logged 3 times in syslog by the 
puppetmaster (in deubg mode).  Manifests are on the puppet master's local disk. 
 Perform the same runs again straight after and both nodes work.  Subsequent 
failures can occur though.  The same behaviour can be seen without MCollective, 
too.

Puppet agent command issued by MCollective is: puppet agent --onetime 
--no-daemonize --verbose --report

The 'missing' class can vary run for run.



-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to