Issue #1178 has been updated by luke.
Status changed from Accepted to Ready for Checkin
Assigned to changed from Luke to jamtur01
I've uploaded what I think are the final fixes to this in the
[tickets/0.24.x/1178] branch.
Here's the changelog I added:
Removed support for the 'node_name' setting in LDAP and external node
lookups.
Also removed support for 'default' nodes in external nodes.
LDAP nodes now use the certificate name, the short name, and 'default',
but external nodes just use the certificate name and any custom terminus
types will use just the certificate name.
----------------------------------------
Bug #1178: Inconsistent node names
http://reductivelabs.com/redmine/issues/show/1178
Author: marthag
Status: Ready for Checkin
Priority: Urgent
Assigned to: jamtur01
Category: unknown
Target version: 0.24.5
Keywords:
Complexity: Unknown
Patch: Tests
Affected version:
Client facts are written to yaml/facts/hostname.yaml, but puppetmaster attempts
to read them from yaml/facts/fqdn.yaml. This causes the facts never to be
updated and new nodes to fail. This started happening when I changed node_name
to facter.
Both client and master are Debian Etch, puppet 0.24.4.
This is related to tickets #1147 and #1168.
There is a workaround, which is to link or copy hostname.yaml to fqdn.yaml.
----------------------------------------
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://reductivelabs.com/redmine/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
-~----------~----~----~----~------~----~------~--~---
