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.
Foreman maintain service status command returns non "0" exit code due to some invalid services like "dynflow-sidekiq@orchestrator.yml.rpmsave, dynflow-sidekiq@worker.yml.rpmsave"
Verified.
Tested on Satellite 6.10.0 Snap 3.0
Version: rubygem-foreman_maintain-0.8.1-1.el7sat.noarch
Setup:
1. Have any backup .rpmsave file in /etc/foreman/dynflow/
# ls /etc/foreman/dynflow/
orchestrator.yml test_bz.yml.rpmsave worker-1.yml worker-hosts-queue-1.yml
Steps:
1. foreman-maintain service status -b
Observation:
service-status doesn't pick up any backup files like *.rpmsave, which don't exist as services.
Also, any other files with extension .yml that don't pick up by service-status, which fail eventually.
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 (Satellite 6.10 Satellite Maintenance Release), 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/RHBA-2021:4697
Verified. Tested on Satellite 6.10.0 Snap 3.0 Version: rubygem-foreman_maintain-0.8.1-1.el7sat.noarch Setup: 1. Have any backup .rpmsave file in /etc/foreman/dynflow/ # ls /etc/foreman/dynflow/ orchestrator.yml test_bz.yml.rpmsave worker-1.yml worker-hosts-queue-1.yml Steps: 1. foreman-maintain service status -b Observation: service-status doesn't pick up any backup files like *.rpmsave, which don't exist as services. Also, any other files with extension .yml that don't pick up by service-status, which fail eventually.