Puppet users - Jul 2014 - Puppet uses catalog of node B for node A

Hello,

I installed puppet 2.6.17, 3.4.3 and finally 3.6.2 on SLES 11 SP1 or SLES 
11 SP3 and always ran in this problem: Puppet is using the wrong catalog on 
some nodes.

I can run „puppet agent –t“ many times on node A without problems. When I 
run „puppet agent –t“ on node B and afterwards on node A, puppet uses the 
catalog of node B for both, node B and node A!
My final tests where done with these packages on the only master with SLES 
11 SP3: 

facter-2.0.0-11.1.x86_64.rpm
puppet-3.6.2-2.2.x86_64.rpm
puppet-server-3.6.2-2.2.x86_64.rpm
ruby-1.8.7.p357-3.7.x86_64.rpm
ruby-devel-1.8.7.p357-4.1.x86_64.rpm
rubygem-hiera-1.2.1-21.3.x86_64.rpm
rubygem-json_pure-1_6-1.6.7-1.19.x86_64.rpm
rubygem-ruby-shadow-2.2.0-11.4.x86_64.rpm
rubygems-1.8.15-27.9.x86_64.rpm

Actually, the first 10 characters of the fqdn's are identical. Can this 
cause the problem?

The clients (SLES 11 SP1) use the same packages. I used „node“ definitions 
as well as hiera to assign my classes to the nodes. No configurations 
concerning environments are done.

Thanks in advance for any help on this!

Kind regards 

Helmut

-- 
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d36bb19d-d418-41c1-90f4-5b1ca7f7a80a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.