#1200: puppetd exits when dns resolution fails and client doesn't have a
certificate yet
-------------------+--------------------------------------------------------
Reporter: diska | Owner: community
Type: defect | Status: new
Priority: normal | Component: client
Version: 0.24.4 | Severity: normal
Keywords: | Stage: Unreviewed
Patch: None | Complexity: Unknown
-------------------+--------------------------------------------------------
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
--
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/1200>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
