Markus Frosch <mar...@lazyfrosch.de> writes:

> On my system the puppet agent starts before the puppetmaster which is
> here the same box.
>
> Due to this, the puppet agent fails on its first run and sends
> warnings about being unable to contact the puppetmaster.

Thank you for the bug report.

A fix for this bug is available in
http://anonscm.debian.org/gitweb/?p=pkg-puppet/puppet.git;a=commitdiff;h=e26520366828d9181a1bf3403a1b65adc18ee628,
and has also been merged for 3.0.2-1, scheduled for unstable/testing
after wheezy is released.

Here's the result of installing and upgrading generated packages of
puppet and puppetmaster 2.7.18-2, and packages with the bugfix applied.
The apache2 package is also installed.

,----[ 2.7.18-2 ]
| S01apache2 -> ../init.d/apache2
| S02puppet -> ../init.d/puppet
| S02puppetmaster -> ../init.d/puppetmaster
`----

,----[ 2.7.18-2 + bugfix ]
| S01apache2 -> ../init.d/apache2
| S02puppetmaster -> ../init.d/puppetmaster
| S03puppet -> ../init.d/puppet
`----

The puppet agent now starts after the puppet master.

> Maybe this is also relevant for wheezy?

Unfortunately, no. It is late in the wheezy freeze, and the severity is
not high enough for an exception, even though the fix is simple.

It is, however, relevant for the next release, as well as an "update"
release for wheezy, and for backports generated from that.

-- 
Stig Sandbeck Mathisen

Attachment: pgpN5sou6E0mT.pgp
Description: PGP signature

Reply via email to