On May 3, 2012, at 8:55 AM, Craig White wrote: > On May 3, 2012, at 6:09 AM, jcbollinger wrote:
>> Very likely you are missing something. Puppet should not even be >> reading both the configure.pp files unless the classes therein are >> both assigned to your node, directly or indirectly. Since you created >> one module by duplicating the other, my guess would be that you missed >> changing one or more namespaces in the copy, leaving them referring to >> the original module. For example, you might have something like this: > So it seems obvious that even though the classes ldap::client_install and > ldap::configure are not in the ENC, not currently being assigned to this > system, the past inclusion is somehow hanging on causing the conflict (and > indeed they are there in /var/lib/puppet/state/classes.txt). So I manually > edit this file, remove the references to them with vi and the next puppet run > they return. ;-( ---- out of sight - out of mind. Even though I'm using foreman as ENC and I would think that /etc/puppet/manifests/nodes.pp (default node) shouldn't have any impact, it clearly did as was doing the dirty deed of adding the classes back in each catalog run. Thanks - solved Craig -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
