Restarting services puts puppet into restart-loop

Bug #1837526 reported by Frank Burkhardt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openssl (Ubuntu)
New
Undecided
Unassigned

Bug Description

Puppet is a configuration and software management system that can be used e.g. for installing and upgrading debian packages, modifying configuration files, etc. Puppet will call apt-get/dpkg when needed to handle packages.

When libssl1.1 is installed/upgraded and the installation process is controlled by Puppet, the automatic re-start of ssl-dependant services Puts puppet into a re-start loop:

   1. libssl1.1 's postinstall script re-starts puppet via systemd (systemctl restart puppet.service)
   2. systemd will terminate all processes associated with the Puppet service
   3. dpkg is among these processes since it's called by Puppet and inherits its cgroup-memberships.
   4. libssl1.1 's postinstall script will never succeed since it's killed by systemd
   5. puppet re-starts
   6. puppet runs "dpkg --configura -a"
   7. libssl1.1 is unconfigured, the postinst script is run
   8. goto 1.

Puppet should be removed from hardcoded list of services to be re-started in libssl1.1's postinst script. A patch to do so is attached.

Revision history for this message
Frank Burkhardt (fbo) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "Removes puppet from list of to-be-re-restarted services" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Adrien Nader (adrien) wrote :

I'm marking this bug as a duplicate of #1971650 . The general goal is to move to needrestart rather than continue using the current postinst script.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.