Stein: systemd stop dependencies broken during reboot/shutdown
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
In Progress
|
High
|
Damien Ciabrini | ||
Bug Description
A paunch container has three systemd files associated with it:
1. tripleo_*.service - the regular systemd service generated by paunch
2. libpod-
process that creates a pidfile for tripleo_*.service and monitor it.
3. libpod-*.scope - created dynamically by runc. for cgroups accounting
Paunch can only set start/stop dependencies on 1., not 2. and 3.
On reboot, systemd is allowed to stop 2. or 3. at any time, which can
cause 1. to stop before its deps as set up by paunch.
To prevent an unexpected stop of 1. from happening, in Master we
inject a additional dependency dynamically in 2. and 3. so that systemd
is forbidden to stop those scopes automatically until
paunch-
That way, when systemd stops 1., the two scopes 2. and 3. will
finish in sequence and paunch dependencies will be respected.
We need to backport that commit in Stein until podman expose a programmatic
API to configure the dependencies as expected.
| Changed in tripleo: | |
| milestone: | none → train-3 |
| milestone: | train-3 → none |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to paunch (stable/stein) | #1 |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to tripleo-heat-templates (stable/stein) | #2 |
| OpenStack Infra (hudson-openstack) wrote Fix merged to paunch (stable/stein) | #3 |
| tags: | added: in-stable-stein |
| OpenStack Infra (hudson-openstack) wrote Fix merged to tripleo-heat-templates (stable/stein) | #4 |
Fix proposed to branch: stable/stein
Review: https:/