Affects Version/s: PUP 3.4.3
Fix Version/s: None
Using the following Puppet packages:
..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.