Taken from https://bugs.launchpad.net/glance/+bug/1855708: "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://review.opendev.org/#/c/697969/5/glance/common/wsgi.py [2] https://github.com/openstack/glance/blob/master/glance/common/utils.py (L560, L561, L562) 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."
The patch from stable/train was automagically picked up downstream and a package was created.
@Abhishek: Can you confirm it's normal that the PID are changing? Does Glance kill and recreate its children upon reloading the configuration?
(In reply to Cyril Roelandt from comment #8) > @Abhishek: Can you confirm it's normal that the PID are changing? Does > Glance kill and recreate its children upon reloading the configuration? Cyril, Yes PID changes during reload/sighup. This is how reloading on sighup works. For example there are 3 glance api children are running and someone issues sighup signal, then it checks whether any of the children is processing any request. If not then it kills that children and spawns new children which contains the new configuration changes. If any of the children is processing request then it waits until that request is processed (graceful shutdown) and once request is completed then it kills that process (child) and spwans new one with ne w PID. There are logs in glance-api which telles child process is killed and new one is popped.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:4284