Issue #12844 has been updated by R.I. Pienaar.
I would argue that the initial change in behaviour is unacceptable this late into stable version of our code. 2.7 has had 11 leases and still it's behaviour keeps changing. Lock files are an external API users depend on it for monitoring and management and our own tool set like mcollective has the behaviours baked in This change in behaviour introduced in 2.7.10 changes those external interfaces and breaks expectations mid production release and should be reverted and retargeted for the next release cycle the mcollective agent simply will not be able to reliably manage this version of puppet now - the one that PE is based on - without changing that agent so we will need to go through that process of testing etc for PE 2.5 if this remains. ---------------------------------------- Bug #12844: Puppet upgrade can't remove lockfile. https://projects.puppetlabs.com/issues/12844#change-55930 Author: Trevor Vaughan Status: Accepted Priority: High Assignee: Chris Price Category: Target version: 2.7.12 Affected Puppet version: 2.7.11 Keywords: lock file, puppet agent, disable, enable Branch: Procedure: Start with 2.7.7 Run puppet agent --disable Upgrade to 2.7.11 Run puppet agent --enable Result: puppet agent --enable does not remove /var/lib/puppet/state/puppetdlock and puppet will no longer run. -- 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.
