yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #67028
[Bug 1702260] Re: nova compute child process remains orphan after sending sigkill or sigterm signal to parent process
nova-compute is using ServiceLauncher to launch the service which
doesn't require any changes to exit gracefully.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1702260
Title:
nova compute child process remains orphan after sending sigkill or
sigterm signal to parent process
Status in OpenStack Compute (nova):
Invalid
Bug description:
When user sends SIGKILL (kill -9) or SIGTERM (kill -15) signal to
nova-comupte parent process then parent process terminates immediately
but child process keeps running forever and keeps processing the
requests received from rabbitmq.
Steps to reproduce:
1. Identify running processes of nova-compute using "ps aux | grep nova-compute'
2. Send kill or terminate signal to parent process.
$ kill -9 <nova-compute-parent-process-id> or kill -15 <nova-compute-parent-process-id>
3. Verify parent process is killed using "ps aux | grep nova-compute'
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1702260/+subscriptions
References