Bug#563559: puppet - Does not start after upgrade
Hi: I've been surprised by the default to no too. While I understand why that's the case (so there's no chance to hijack the system by a rogue puppetmaster upon puppet client installalation), I don't see why the option is not managed by debconf defaulting to no (won't start at boot time). This way, you can have a secured install on unmanaged environments while making things easier for those that understand the implications but still want/need the package to autoconfigure the system when installed (currently it basically blocks an automatic deploy unless you release a local puppet package). Cheers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563559: puppet - Does not start after upgrade
On Thu, 2 Dec 2010 21:47:26 +0100, =?UTF-8?Q?Jes=C3=BAs?= M. Navarro jesus.nava...@undominio.net wrote: While I understand why that's the case (so there's no chance to hijack the system by a rogue puppetmaster upon puppet client installalation), I don't see why the option is not managed by debconf defaulting to no (won't start at boot time). I think that if we received a patch to add that, it would be accepted. micah pgpwGyWGS8rq6.pgp Description: PGP signature
Bug#563559: puppet - Does not start after upgrade
tag 563559 + confirmed severity 563559 minor thanks Hello, and thanks for reporting this issue. The change to make puppetd not start at boot is by design, and is documented in NEWS.Debian, as well as on the console when installing. It is, perhaps, unfortunate that it also affects clients upgrading. I'll reduce the severity level of this bug to minor, since this issue does not seem to match the description for grave: # grave - makes the package in question unusable or mostly so, or # causes data loss, or introduces a security hole allowing access to the # accounts of users who use the package We could possibly add a section to the package post installation script to make puppetd start at boot if the package is being upgraded from a previous version of puppetd, so I'll keep this bug open until we decide if and how to do so. -- Stig Sandbeck Mathisen pgpFmGysoY7oN.pgp Description: PGP signature
Bug#563559: puppet - Does not start after upgrade
Package: puppet Version: 0.25.1-3 Severity: grave puppet does not longer start after the upgrade from lenny to squeeze. | Preparing to replace puppet 0.24.5-3 (using .../puppet_0.25.1-3_all.deb) ... | Stopping puppet configuration management tool. | Unpacking replacement puppet ... | Processing triggers for man-db ... | Setting up puppet (0.25.1-3) ... | Installing new version of config file /etc/default/puppet ... | Installing new version of config file /etc/logcheck/ignore.d.server/puppet ... | Installing new version of config file /etc/init.d/puppet ... | Starting puppet configuration management tool | puppet not configured to start, please edit /etc/default/puppet to enable | . Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, Errand of Mercy, stardate 3198.9 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
