Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2067120 - Warning: Stopping foreman.service, but it can still be activated by: foreman.socket, when calling foreman-maintain service restart
Summary: Warning: Stopping foreman.service, but it can still be activated by: foreman....
Keywords:
Status: CLOSED DUPLICATE of bug 2154917
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.10.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Gaurav Talreja
URL:
Whiteboard:
: 2081714 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-23 11:11 UTC by Evgeni Golov
Modified: 2023-01-26 13:50 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1964394
Environment:
Last Closed: 2023-01-26 13:50:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-14727 0 None None None 2023-01-05 16:25:18 UTC

Description Evgeni Golov 2022-03-23 11:11:17 UTC
+++ 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).

Comment 2 Eric Helms 2022-05-10 00:20:59 UTC
*** Bug 2081714 has been marked as a duplicate of this bug. ***

Comment 7 Eric Helms 2023-01-26 13:50:07 UTC

*** This bug has been marked as a duplicate of bug 2154917 ***


Note You need to log in before you can comment on or make changes to this bug.