[Expired for puppet (Ubuntu) because there has been no activity for 60
days.]
** Changed in: puppet (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.
On 12/01/2014 07:31 PM, Robie Basak wrote:
> What is it trying to look up? Itself, or something else? I'd expect a
> self-lookup to always succeed.
It tries to look up the Puppet server, to fetch a certificate from.
Maybe it also tries to look up itself. But that would succeed, indeed.
> If for so
What is it trying to look up? Itself, or something else? I'd expect a
self-lookup to always succeed.
If for some reason it does need to hit the network in the typical case,
then I agree that a timeout may make sense. In this case, I suggest
going to upstream to implement proper retry functionality
On 12/01/2014 06:49 PM, Robie Basak wrote:
> Then isn't something else broken that causes puppet to be started before
> hostname resolution is available? What is on your system that causes
> hostname resolution to not be available? Can we fix that instead?
>
Perhaps we can. Puppet runs from a Syst
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
> It may be running before hostname resolution is available.
Then isn't something else broken that causes puppet to be started before
hostname resolution is available? What is on your system that causes
hostname r
