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 1966418 - foreman-maintain shows warning to run 'systemctl daemon-reload' each time I restart services.
Summary: foreman-maintain shows warning to run 'systemctl daemon-reload' each time I r...
Keywords:
Status: CLOSED DUPLICATE of bug 1965901
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Anurag Patel
QA Contact: Gaurav Talreja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-01 06:28 UTC by Jameer Pathan
Modified: 2021-06-01 09:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-01 09:12:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jameer Pathan 2021-06-01 06:28:08 UTC 
Description of problem:
foreman-maintain shows warning to run 'systemctl daemon-reload' each time I restart services.

Version-Release number of selected component (if applicable):
- Satellite 6.10.0 snap 2
- rubygem-foreman_maintain-0.8.1-1.el7sat.noarch

How reproducible:
- Always

Steps to Reproduce:
1. foreman-maintain service restart

Actual results:
- If I don't run `systemctl daemon-reload` after service restart some of satellite task fails. e.g repo sync, adding rh cloud token for insights etc.

[root@dhcp-2-149 ~]# 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]      
--------------------------------------------------------------------------------

[root@dhcp-2-149 ~]# systemctl daemon-reload


Expected results:
- No need to run `systemctl daemon-reload` manually each time after foreman-maintain service restart.

Additional info:
Comment 2 Evgeni Golov 2021-06-01 08:50:26 UTC 
I don't think the component (Foreman Maintain) is correct.

If this is a freshly deployed machine (or a fresh upgrade), the Installer should have kicked systemd accordingly after modifying the file.
If it didn't, that's an Installer bug.

At the same time, the attached traceback doesn't show anything about *why* things are not working.
So please provide a full one, or a reproducer machine.
Comment 3 Jameer Pathan 2021-06-01 09:12:04 UTC 

*** This bug has been marked as a duplicate of bug 1965901 ***
Note You need to log in before you can comment on or make changes to this bug.