Designate-api/central children workers are not getting killed on service stop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Issue:
When I stop designate-api service, its children workers does not get killed. It left orphaned. Same issue with designate-central and designate-worker.
Analysis:
Before Stopping service:
-------
```
ps -fe | grep designate-api
designa+ 2722054 1 0 17:45 ? 00:01:31 /usr/bin/python3 /usr/bin/
designa+ 2722102 2722054 0 17:45 ? 00:00:03 /usr/bin/python3 /usr/bin/
designa+ 2722103 2722054 0 17:45 ? 00:00:02 /usr/bin/python3 /usr/bin/
```
It shows that there is one main process and 2 child process of designate-api working.
```
ss -tunlp | grep 9001
tcp LISTEN 0 128 0.0.0.0:9001 0.0.0.0:* users:(
```
After stopping service:
-------
systemctl stop designate-api
```
ps -fe | grep designate-api
designa+ 2722102 1 0 17:45 ? 00:00:03 /usr/bin/python3 /usr/bin/
designa+ 2722103 1 0 17:45 ? 00:00:02 /usr/bin/python3 /usr/bin/
```
We can see that child workers become orphaned. It does not get killed.
Server is still listening on port 9001.
ss -tunlp | grep 9001
tcp LISTEN 17 128 0.0.0.0:9001 0.0.0.0:* users:(
Environment Openstack / Designate version - Stable/Train
This is most likely the same as this bug https:/ /bugs.launchpad .net/designate/ +bug/1857476
Fixed in this commit https:/ /github. com/openstack/ designate/ commit/ 7600620be8a2dd6 b014ebd3d989139 3f8b2ea7e7