Reload functionality is broken in Ussuri
Bug #1867205 reported by
Abhishek Kekane
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
New
|
High
|
Unassigned | ||
Bug Description
Reload config files doesn't work upon sending sighup signal to glance-api service parent process, resulting in terminating the parent and keeping child processes orphan.
Revision history for this message
| Abhishek Kekane (abhishek-kekane) wrote | #1 |
| Changed in glance: | |
| importance: | Undecided → High |
To post a comment you must log in.
We have removed ssl support [1] this cycle which results in removing some ssl related config options, but we didn't removed all of its usage and two config options 'key_file' and 'cert_file' are still used in reload functionality [2] which is causing error when SIGHUP is sent to parent process and results in termination due to error and childs remaining stale.
If I comment/remove those two options from [2] then SIGHUP works just fine.
[1] https:/
[2] https:/
I have verified the same by adding new store to enabled_backends config option and it is crating the new store (file) as well as adding image to this newly created store.