SIGHUP's effect on parameters is not well defined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
If I start the api server using:
$ cd /opt/stack/cinder && /usr/local/
and, using a debug statement, print out the value of the 'glance_
+++ b/cinder/
@@ -330,6 +330,8 @@ class API(base.Base):
if filters:
+ LOG.debug("CONF %s" % str(CONF.
then do a 'cinder list' to trigger the debug I see the default values for this parameter:
5f00a82aa4004b
If I then edit /etc/cinder/
glance_
and finally do a SIGHUP on the parent cinder api process:
cinder$ ps auwx |grep cinder-api |grep -v grep
ubuntu 24044 0.6 0.3 215004 61040 pts/23 S 15:08 0:07 /usr/bin/python /usr/local/
ubuntu 24052 0.0 0.4 305112 65736 pts/23 S 15:08 0:00 /usr/bin/python /usr/local/
cinder$ kill -HUP 24044
(and check the same process ids exist as before):
cinder$ ps auwx |grep cinder-api |grep -v grep
ubuntu 24044 0.6 0.3 215004 61040 pts/23 S 15:08 0:07 /usr/bin/python /usr/local/
ubuntu 24052 0.0 0.4 305112 65736 pts/23 S 15:08 0:00 /usr/bin/python /usr/local/
what I find is that the new value of the glance_
2014-09-02 15:10:34.561 DEBUG cinder.volume.api [req-0c29fa25-
but ... the entries in /etc/cinder/
For example, if osapi_volume_
Changes to any parameters which are configured at start up of the service (including debug = True/False) do not get picked up after a SIGHUP. The impact of a change to some parameters (eg 'lock_path') is not clear. The only way for an operator to figure out which parameters will be updated after a SIGHUP is by looking through the code, or trial and error. If a SIGHUP does pick up a change to a parameter an operator still can't be sure that it's safe to make that change or not (eg 'lock_path').
summary: |
- SIGHUP effect on parameters not well defined + SIGHUP's effect on parameters is not well defined |
Changed in cinder: | |
status: | New → Confirmed |
assignee: | nobody → Ivan Kolodyazhny (e0ne) |
Changed in cinder: | |
assignee: | nobody → Michael Dovgal (mdovgal) |
Also related, (but possibly a separate bug) if I do
$ nc localhost 8776
prior to the SIGHUP
then no requests sent after the SIGHUP are processed until that (unauthenticated) client connection is killed.