Issue #9597 has been updated by Ashley Penney.
This was on 2.7.x, I'm not sure exactly which version - whatever was the latest when I filed the ticket! In step 5 it gets the correct changed hostname (rc.local checks for passed in ec2 data to set the correct hostname). It's the copy of puppet that remains running as a daemon that uses the original hostname when the machine first boots. If you need I can check if this still happens tomorrow by messing around with AMIs and making sure puppet is fully up to date. ---------------------------------------- Bug #9597: Puppetd doesn't know a hostname changed. https://projects.puppetlabs.com/issues/9597 Author: Ashley Penney Status: Needs More Information Priority: Normal Assignee: Ashley Penney Category: Target version: Affected Puppet version: Keywords: Branch: Order of events: <pre> 1/ Provision EC2 machine 2/ Hostname is 10-1gibberish 3/ Puppet starts as a daemon 4/ Hostname changes due to rc.local 5/ puppetd -tv runs to trigger a cert request 6/ Cert request is signed 7/ Running puppetd triggers again and fails to retrieve cert 8/ puppetd -tv manually run works fine. </pre> It seems that once puppetd starts up it doesn't know if the hostname of the server changes. This causes me grief when trying to get EC2 hosts up :) -- 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.
