Public bug reported:
Nova compute service does not listen to sighup signal actually it should
reload the configuration file.
Steps to reproduce:
1. Run nova compute service as a daemon
2. Send sighup signal "kill -1 $parent_id_of_compute_service" or "kill -HUP
$parent_id_of_compute_service"
Whereas if you send sighup signal to nova-api or nova-conductor then it
reloads the configuration files.
** Affects: nova
Importance: Undecided
Status: New
--
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/1705680
Title:
nova compute does nothing on receiving sighup signal
Status in OpenStack Compute (nova):
New
Bug description:
Nova compute service does not listen to sighup signal actually it
should reload the configuration file.
Steps to reproduce:
1. Run nova compute service as a daemon
2. Send sighup signal "kill -1 $parent_id_of_compute_service" or "kill -HUP
$parent_id_of_compute_service"
Whereas if you send sighup signal to nova-api or nova-conductor then
it reloads the configuration files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1705680/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
