| 2021-07-18 23:54:46 |
Takashi Kajinami |
description |
Description
===========
Currently SIGHUP is widely used to reload services inside containers.
However swift processes doesn't use SIGHUP to reload config files but to terminate processes.
For server processes we should use SIGUSR1 instead while daemon processes doesn't support reloading configuration files.
Steps to reproduce
==================
* Check /etc/systemd/system/multi-user.target.wants/tripleo_swift*.service
Expected result
===============
* SIGUSR1 is used to reload server services
* No ExecReload is defined for daemon services
Actual result
=============
* SIGHUP is used for all services for reload
Environment
===========
The issue was initially found in stable/train deployment
Logs & Configs
==============
N/A |
Description
===========
Currently SIGHUP is widely used to reload services inside containers.
However swift processes don't use SIGHUP to reload config files but to terminate processes.
For server processes we should use SIGUSR1 instead while daemon processes doesn't support reloading configuration files.
Steps to reproduce
==================
* Check /etc/systemd/system/multi-user.target.wants/tripleo_swift*.service
Expected result
===============
* SIGUSR1 is used to reload server services
* No ExecReload is defined for daemon services
Actual result
=============
* SIGHUP is used for all services for reload
Environment
===========
The issue was initially found in stable/train deployment
Logs & Configs
==============
N/A |
|
