yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #09369
[Bug 1276694] Re: Openstack services should support SIGHUP signal
murano-api, murano-conductor are affected, see
https://github.com/stackforge/murano-api/blob/master/muranoapi/openstack/common/service.py
https://github.com/stackforge/murano-conductor/blob/master/muranoconductor/openstack/common/service.py
** Also affects: murano
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1276694
Title:
Openstack services should support SIGHUP signal
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Status in Murano Project:
New
Status in Oslo - a Library of Common OpenStack Code:
Invalid
Bug description:
In order to more effectively manage the unlinked and open (lsof +L1)
log files descriptors w/o restarting the services, SIGHUP signal
should be accepted by every Openstack service.
That would allow, e.g. logrotate jobs to gracefully HUP services after
their log files were rotated. The only option we have for now is to
force the services restart, quite a poor option from the services
continuous accessibility PoV.
Note: according to http://en.wikipedia.org/wiki/Unix_signal
SIGHUP
... Many daemons will reload their configuration files and reopen their logfiles instead of exiting when receiving this signal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1276694/+subscriptions