Designate-api/central children workers are not getting killed on service stop

Bug #1915756 reported by Rajat Jain
6
This bug affects 1 person
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/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722102 2722054 0 17:45 ? 00:00:03 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722103 2722054 0 17:45 ? 00:00:02 /usr/bin/python3 /usr/bin/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
```

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:(("designate-api",pid=2722103,fd=8),("designate-api",pid=2722103,fd=5),("designate-api",pid=2722102,fd=8),("designate-api",pid=2722102,fd=5),("designate-api",pid=2722054,fd=5))
```

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/designate-api --config-file /etc/designate/designate.conf --log-file /var/log/designate/api.log
designa+ 2722103 1 0 17:45 ? 00:00:02 /usr/bin/python3 /usr/bin/designate-api --config-file /etc
```

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:(("designate-api",pid=2722103,fd=5),("designate-api",pid=2722102,fd=5))

Environment Openstack / Designate version - Stable/Train

Rajat Jain (rajjai)
description: updated
Revision history for this message
Erik Olof Gunnar Andersson (eandersson) wrote :
Revision history for this message
Erik Olof Gunnar Andersson (eandersson) wrote :

A new build was released earlier today for Train. Are you able to retest against that release?
https://github.com/openstack/designate/releases/tag/9.0.2

Revision history for this message
Rajat Jain (rajjai) wrote :
Download full text (3.5 KiB)

Hey Eric, thank you for throwing light on this issue. It really helps.I saw that newer release has the fixed code.
Unfortunately, I am not able to update it.
Seems my repo mirror does not have newer release yet.

[HOST ~]# yum upgrade openstack-designate-api
Repository 'CentOS-PowerTools' is missing name in configuration, using id.
Repository 'centos-messaging-rabbitmq' is missing name in configuration, using id.
Repository 'epel-boost' is missing name in configuration, using id.
Repository 'epel-nagios' is missing name in configuration, using id.
CentOS-8 - AppStream 19 MB/s | 6.3 MB 00:00
CentOS-8 - Base 6.1 MB/s | 2.3 MB 00:00
CentOS-8 - Ceph Nautilus 925 kB/s | 412 kB 00:00
CentOS-8 - Extras 30 kB/s | 8.6 kB 00:00
CentOS-PowerTools 4.5 MB/s | 2.0 MB 00:00
elastic beats repo 84 MB/s | 20 MB 00:00
centos-messaging-rabbitmq 265 kB/s | 137 kB 00:00
epel-boost 6.9 MB/s | 8.9 MB 00:01
epel-nagios 3.4 MB/s | 8.9 MB 00:02
ICINGA (stable release for epel) 939 kB/s | 192 kB 00:00
InfluxData Repository - CentOS 8 377 kB/s | 30 kB 00:00
Puppet 5 Repository el 8 - x86_64 16 MB/s | 21 MB 00:01
RDO CentOS-8 - QEMU EV ...

Read more...

Revision history for this message
Rajat Jain (rajjai) wrote :

Hi, Any idea on above?

Revision history for this message
Rajat Jain (rajjai) wrote :

Got the version update today! it is fixed now :)

Changed in designate:
status: New → Fix Released
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.