Issue #3580 has been updated by Alan Barrett.

I am using 0.25.4 on both the client and server.

Further testing suggests that puppetmasterd is calling the node classifier for 
real client connections, but not for "--compile".  My node classifier logs the 
date and the command line arguments to a file, and that file does not grow when 
I run "puppetmasterd --compile ${myclient}".

----------------------------------------
Bug #3580: node_classifier should be invoked on every connection
http://projects.puppetlabs.com/issues/3580

Author: Alan Barrett
Status: Needs more information
Priority: Normal
Assigned to: Luke Kanies
Category: node
Target version: 
Affected version: 0.25.4
Keywords: 
Branch: 


The external node classifier script (referred to by the "node_classifier" 
variable in the [puppetmasterd] section of puppet.conf) is not invoked every 
time a client connects.  If the same client connects multiple times, or if 
"puppetmasterd --compile ${nodename}" is executed multiple times, then it 
appears that the node classifier script is executed only once per client name.

This is bad because the external node classifier might have some configuration 
that changes without puppet's knowledge, and puppet will not notice such 
changes if it doesn't invoke the node classifier script again.

I would prefer to have the node classifier invoked on every connection.  
Failing that, it would be OK if the information were cached for a time not 
exceeding the "filetimeout" setting (which defaults to 15 seconds).


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to