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.

Description of problem:



`satellite-maintain service stop --only foreman`
 and then 
`satellite-maintain service start --only foreman`

and then

`satellite-maintain service status`
I see not all services are running again

 "Some services are not running (dynflow-sidekiq@orchestrator, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1".

Version-Release number of selected component (if applicable):
Sat 6.11.0 snap_version: '26.0'
~]# rpm -q satellite
satellite-6.11.0-2.el8sat.noarch
~]# rpm -q foreman
foreman-3.1.1.21-1.el8sat.noarch


How reproducible:
Every time


Steps to Reproduce:
1. satellite-maintain service stop --only foreman
2. satellite-maintain service start --only foreman
3. satellite-maintain service status

Actual results:
 "Some services are not running (dynflow-sidekiq@orchestrator, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1".

Expected results:
All services are running.


Additional info:

I will attach logs.

Hi

this does not appear to be a regression, process works OK in 6.10.7

Tested on
~]# rpm -q satellite
satellite-6.10.7-1.el7sat.noarch

~]# rpm -q foreman
foreman-2.5.2.21-1.el7sat.noarch

I will attach logs.

(In reply to Stephen Wadeley from comment #2)
> Hi
> 
> this does not appear to be a regression, process works OK in 6.10.7
> 
sorry, that is a regression (does not happen on previous major version).

This is generally speaking intended behaviour and starting just the foreman service is not something we would suggest. If you can clarify in what scenario one would stop and then start only the foreman service (versus using restart).