Issue #1200 has been updated by jamtur01. Status changed from Ready for Checkin to Closed
Pushed in commit:"6764af3c196a526647eb4a270ec737e2b0f20d36" to 0.24.x stable. ---------------------------------------- Bug #1200: puppetd exits when dns resolution fails and client doesn't have a certificate yet http://reductivelabs.com/redmine/issues/show/1200 Author: diska Status: Closed Priority: Normal Assigned to: jamtur01 Category: executables Target version: 0.24.5 Complexity: Easy Patch: Code I'm using preseeding to install Ubuntu workstations and I'm installing puppet as part of the installation process. The puppetmaster has autosigning enabled and the idea is that after the Ubuntu installation finishes the puppet client takes over and finishes the configuration. However, because Ubuntu uses [[NetworkManager]], the network is not up when the puppet client gets started. This causes 2 problems: First off it can't resolve the puppet hostname, and that causes the 2nd problem: it can't get a certificate. After that the client exits where I expected it to sleep and try again every 30 minutes. First I thought this was a problem with Ubuntu because it launches puppetd with "-w 0", but when I invoked puppetd from the commandline with "puppetd --no-daemonize --verbose" it exited as well. These tests were done with Ubuntu Hardy using their package puppet-0.24.4-3 ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
