+++ This bug was initially created as a clone of Bug #1964394 +++
Description of problem: Some of the warning messages comes in satellite services restart
Version-Release number of selected component (if applicable):
6.10.0
How reproducible:
always
Steps to Reproduce:
1. Install Satellite with 6.10 snap1.
2. Restart the Satellite services
3. Some of the warning messages displayed in service stop and start
# foreman-maintain service restart
Running Restart Services
================================================================================
Check if command is run as root user: [OK]
--------------------------------------------------------------------------------
Restart applicable services:
Stopping the following service(s):
rh-redis5-redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-resource-manager, rh-redis5-redis, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
\ stopping puppetserver
Warning: Stopping foreman.service, but it can still be activated by:
foreman.socket
| stopping rh-redis5-redis
Warning: postgresql.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: Stopping pulpcore-api.service, but it can still be activated by:
pulpcore-api.socket
Warning: Stopping pulpcore-content.service, but it can still be activated by:
pulpcore-content.socket
/ All services stopped
Starting the following service(s):
rh-redis5-redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-resource-manager, rh-redis5-redis, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
\ starting rh-redis5-redis
Warning: postgresql.service changed on disk. Run 'systemctl daemon-reload' to reload units.
/ All services started [OK]
Actual results:
Warning messages come in satellite service restart
Expected results:
Warning message should not come in satellite service restart
Additional info:
--- Additional comment from Evgeni Golov on 2022-03-17 10:48:23 UTC ---
I've proposed a patch upstream to fix the PostgreSQL part of the warnings:
Warning: postgresql.service changed on disk. Run 'systemctl daemon-reload' to reload units.
However this will not affect the socket ones:
Warning: Stopping foreman.service, but it can still be activated by:
foreman.socket
Warning: Stopping pulpcore-api.service, but it can still be activated by:
pulpcore-api.socket
Warning: Stopping pulpcore-content.service, but it can still be activated by:
pulpcore-content.socket
Those can be fixed if we stop (and start) the sockets in foreman-maintain too. [The stop needs to happen *before* the service stop].
However, I'd argue that this BZ should be split up in two, one fore PostgreSQL (1964394), one for sockets (this one).