The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Upgrade from PE2.0.3 to PE2.5 external_node permission changes
|Assignee:||Moses Mendoza||% Done:|
|Category:||installer||Estimated time:||0.50 hour|
|Branch:||Affected PE version:||2.5.0|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
Hi, I’ve just upgraded a couple of hosts from PE 2.0.3 to 2.5. I’ve noticed that the external_node script in /etc/puppetlabs/puppet-dashboard gets the wrong permissions.
Before: -rwxr-xr-x 1 root root 125 2012-03-26 22:39 external_node
After: -rw-r——– 1 puppet-dashboard puppet-dashboard 125 2012-03-07 03:24 external_node
This obviously breaks the ENC functionality of the dashboard.
This can been seen in Puppet Master debug output as:
debug: Executing ‘/etc/puppetlabs/puppet-dashboard/external_node client-hostname’ debug: Empty response for client-hostname from exec terminus err: Could not find node ‘client-hostname’; cannot compile debug: Received report to process from client-hostname debug: Processing report from client-hostname with processor Puppet::Reports::Https err: Report processor failed: Connection refused – connect(2) debug: Processing report from client-hostname with processor Puppet::Reports::Store