Issue #14995 has been reported by Peter Lieverdink.
----------------------------------------
Bug #14995: Partial repository update causes puppetmaster removal
https://projects.puppetlabs.com/issues/14995
Author: Peter Lieverdink
Status: Unreviewed
Priority: Normal
Assignee:
Category: package
Target version:
Affected Puppet version:
Keywords:
Branch:
I've hit a slight snag twice now where puppetmaster, puppetmaster-common and
puppetmaster-passenger were automagically uninstalled from my Debian Squeeze
puppetmaster. (That might mean this needs to go in the 'Doh!' category ;-) I
just reinstalled it after the first time, and put it down as one of those
things. The second time I had a little dig and found out **why** it had
happened.
I use the Puppet Labs repo and the puppet client is managed by puppet, with an
"ensure => latest;" rule.
It would seem that puppet_2.7.14-2puppetlabs1 and
puppet-common_2.7.14-2puppetlabs1 hit your repo some time before
puppetmaster_2.7.14-2puppetlabs1 did. Unfortunately, puppetmaster has a
versioned depend on puppet-common. This meant that aptitude uninstalled
puppetmaster, as its (2.7.14-1puppetlabs1) depend could not be satisfied by the
new puppet-common package.
As the aptitude log says:
Aptitude 0.6.3: log report
Thu, Jun 7 2012 13:45:19 +1000
IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.
Will install 2 packages, and remove 3 packages.
1102 kB of disk space will be freed
===============================================================================
[REMOVE, DEPENDENCIES] puppetmaster
[REMOVE, DEPENDENCIES] puppetmaster-common
[REMOVE, DEPENDENCIES] puppetmaster-passenger
[UPGRADE] puppet 2.7.14-1puppetlabs1 -> 2.7.14-2puppetlabs1
[UPGRADE] puppet-common 2.7.14-1puppetlabs1 -> 2.7.14-2puppetlabs1
===============================================================================
Log complete.
Of course, that breaks the whole infrastructure.
It's quite possible that the fix is for me to not manage the puppetmaster via
puppet, but perhaps changing the versioned puppet-common depend on puppetmaster
from *=* to *>=* is a workable fix. Alternatively, perhaps a *Breaks:
puppetmaster < ${version}* could be set on the puppet-common package.
--
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://projects.puppetlabs.com/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.
