Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When restarting just foreman service, any new task invoked after the restart gets stuck in planned/pending forever.
Version-Release number of selected component (if applicable):
6.11.4
6.12
How reproducible:
100%
Steps to Reproduce:
1. Run a REX job (say execute "date command) just to see it works well.
2. satellite-maintain service restart --only=foreman.service
3. Repeat 1
4. satellite-maintain service restart --only=dynflow-sidekiq@orchestrator,dynflow-sidekiq@worker-1,dynflow-sidekiq@worker-2,dynflow-sidekiq@worker-hosts-queue-1
5. Repeat 1
Actual results:
3. gets stuck forever
5. jobs+tasks start to work again (including those invoked in 3)
Expected results:
3. tasks are completed as usual
Additional info:
Observation: Just restarting dynflow orchestrator service is not sufficient.
dynflow-sidekiq@* services are tied to the foreman service using the PartOf stanza on the systemd service definition level. For some reason, satellite-maintain service restart --only foreman.service brings down the entire group, but then starts only foreman. Is it possible that satellite-maintain does a stop followed by a restart instead of a direct restart?
Native systemctl restart foreman does not suffer from this issue.
Alternatively, setting WantedBy=foreman.service on dynflow-sidekiq@* seems to work too, although the services have to be re-enabled in order for the changes to propagate.
Verified on 6.14 snap 4
satellite-maintain service restart --only=foreman.service is correctly restarting services
Steps:
1. Run a REX job (say execute "date command) just to see it works well.
2. satellite-maintain service restart --only=foreman.service
3. Repeat 1
Results:
Both executions are successful.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.14 security and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:6818