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:
We just saw the CEE introduction to the self-upgrade of foreman-maintain and it appears that it's rather difficult to detect that a self-upgrade happened, and that a 2nd call is necessary, making automation difficult.
Version-Release number of selected component (if applicable):
6.8.z
How reproducible:
Always
Steps to Reproduce:
1. create a playbook which automates the upgrade of Satellite
2. how do you decide that you need to call foreman-maintain twice
Actual results:
return code is 0 and the message isn't very easy to parse and not promised to be stable.
Expected results:
either a specific return code which can be checked and/or a "stable" parsable output (one that won't change with each version, specific enough, etc), so that one can easily detect if a re-run is necessary.
Additional info:
Amit and Mike told me to open this BZ so I do it :-)
As per /usr/include/sysexits.h which recommends user-defined exit codes may be between 64-78, an exit code of 75 may be returned indicating the user/script may retry the command.
Verified:
Verified with:
- foreman-maintain v0.6.9
Test steps:
- Run 'foreman-maintain upgrade check/run'
Observation:
- now self upgrade returns status code 75 which means 'Temporary failure and user intervention is required'.
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.8 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-2020:4365