Puppet users - Feb 2014 - non existing classes cause puppet 2.7 client to error out

I put this up on the Puppet Ask forum as well.  Hopefully the duplication 
isn't a big deal, I've been struggling to come up with a good solution
to
this.

I'm attempting to migrate a puppet environment from Puppet 2.6 to Puppet 
2.7.  My plan for doing this is to install a new Puppet 2.7 master, point 
the 2.6 clients to this new master, and then later update the 2.6 clients 
over a period of time.

However, I'm running into an issue due to the way our external node 
classifier works.  The node classifier returns a number of classes for each 
host.  These classes may or may not be defined in puppet manifests.  In 
2.6, puppet just ignored any classes that were not recognized.  In 2.7, the 
client errors out and fails to pull down any of its configuration, even 
from classes that are defined.  From reading the forums and bug reports, it 
appears that this new behavior is by design.  My question then is, is there 
any way to revert to the previous behavior?  

It is not possible at this time to change the way our ENC works.  My 
workaround will be to identify all undefined classes, and define them as 
empty classes in a puppet manifest.  This is not ideal because new 
undefined classes can be introduced by our ENC as we deploy new machines.  
So it would be an ongoing maintenance process.

-- 
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/c9ee2f95-2572-40d2-993d-226ed2783070%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.