containers are not gracefully stopped on shutdown/reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Alex Schultz |
Bug Description
There is no mechanism to gracefully shutdown containers when shutting down/rebooting a node. They keep running until systemd performs a process cleanup and sends SIGTERM to all running process. If they are still running for some interval after the SIGTERM, systemd sends SIGKILL. It is unknown what impact that this might have.
Example from console logs:
[ 1556.163360] type=1700 audit(152995512
[ 1558.874838] systemd-
[ 1558.886653] systemd-
[ 1558.892701] systemd-
[ 1558.897848] systemd-
[ 1558.903574] systemd-
[ 1558.909220] systemd-
[ 1558.914799] systemd-
[ 1558.920219] systemd-
[ 1558.924792] systemd-
[ 1558.932073] systemd-
[ 1558.943927] systemd-
[ 1558.952055] systemd-
[ 1558.956779] systemd-
[ 1558.961131] systemd-
It's worth noting that projects like neutron refined the systemd service behavior over years including the addition of order-dependent cleanup oneshot services like "neutron-
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → stein-1 |
Changed in tripleo: | |
status: | Triaged → Fix Released |
assignee: | nobody → Alex Schultz (alex-schultz) |
tags: | added: queens-backport-potential |
Related fix https:/ /review. openstack. org/#/c/ 578614