Since your default group is environment1, you don't need a site.pp as your ENC (puppet PE) has already classified this node to environment1. It sounds like the modules in environment1 conflict with the modules in the PE Mcollective Node group which is usually defined for all nodes. What do you have in your example1/modules?
On Monday, December 8, 2014 12:08:22 AM UTC-6, ezzobad wrote: > > Hi, > > This is the configuration: > *Puppet version:* 3.7.2 (Puppet Enterprise 3.7.0) > *OS on the puppet master and agent:* CentOS release 6.5 (Final) > *Puppet server:* Cent200.example.com > *Puppet node:* Cent201.example.com > > environment1: > /etc/puppetlabs/puppet/environments/environment1/ > ├── manifests > │ └── site.pp > └── modules > > and site.pp is an empty file. > > A new node group: *nodegroup1 *(the parent is "*default*" and the > environment is "*environment1*".) > > If I assign a node to this node group (so the only matching node is > cent201.example.com). > > I expect to have no problem by running "puppet agent -t" on the client > side (because site.pp is empty), but looks like there is a conflict: > > *"Classification failed for cent201.example.com > <http://cent201.example.com> due to a classification conflict: The node was > classified into groups named "nodegroup1" and "PE MCollective" that defined > conflicting values for the environment, ."* > Thanks in advance, > Mehdi > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6c8b613a-e6bf-4b93-9415-0674e835c4a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
