DevStack kills services non-gracefully with systemd 219
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
Michal Dulko |
Bug Description
This happens when using older systemd (this is CentOS 7.4.1708):
[stack@localhost kuryr-kubernetes]$ yum info systemd
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: centos2.hti.pl
* epel: ftp.icm.edu.pl
* extras: mirror-
* updates: mirror-
Installed Packages
Name : systemd
Arch : x86_64
Version : 219
Release : 42.el7_4.4
Size : 21 M
Repo : installed
From repo : updates
Summary : A System and Service Manager
(...)
DevStack sets [1] TimeoutStopSec to "infinity". This is a special value that isn't supported on older systemd's:
(...)
Pass "0" to disable the timeout logic. Defaults to DefaultTimeoutS
This results in systemd sending SIGKILL services almost instantly when stopping. Often services processes get orphaned as master process doesn't stop them in time.
I think it would be best to set the default value to a sane, finite number - like 120.
Fix proposed to branch: master /review. openstack. org/519665
Review: https:/