Cannot stop cinder-backup with systemd or SIGTERM

Bug #1523598 reported by Anthony
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Won't Fix
Undecided
Ravi Shekhar Jethani

Bug Description

On Juno release, we are not able to stop cinder-backup:

# rpm -qa '*cinder*'
python-cinder-2014.2.3-3.el7.noarch
openstack-cinder-2014.2.3-3.el7.noarch
python-cinderclient-1.1.1-1.el7.centos.noarch

# systemctl start openstack-cinder-backup
-> OK

# systemctl status openstack-cinder-backup
-> Active: active (running)

# systemctl stop openstack-cinder-backup
-> Error - timeout after 90 seconds

Sending SIGTERM directly to the process gives the same result. In the log, we can see the signal is trapped (Caught SIGTERM, exiting...) but nothing happens.

Please find attached cinder-backup log file with only start/stop of the daemon.

Regards

Revision history for this message
Anthony (anthony-chevalet) wrote :
Revision history for this message
Anthony (anthony-chevalet) wrote :

cinder-backup cannot be managed by pacemaker because of this problem.

summary: - Cannot stop cinder-backup
+ Cannot stop cinder-backup with systemd or SIGTERM
Changed in cinder:
assignee: nobody → Ravi Shekhar Jethani (ravishekar-jethani)
Revision history for this message
Michal Dulko (michal-dulko-f) wrote :

This isn't reproducible on master and Juno is only security supported now [1].

[1] https://wiki.openstack.org/wiki/Releases

Changed in cinder:
status: New → Won't Fix
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.