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.
Created attachment 1482367[details]
cli output
Description of problem:
Running "foreman-maintain upgrade run --target-version 6.4 -y"
If "Upgrade Step: Running installer..." step fails it continues with "Upgrade Step: remove_legacy_mongo..." which resulted in breaking mongo and running "satellite-installer --upgrade" failing.
When a step fails we should exit straight away
Version-Release number of selected component (if applicable):
6.3.3 -> 6.4.beta upgrade.
This step actually are not defined in the foreman-maintain, but rather in the installer hooks, most of them are defined in a way, that they are not run unless installer succeeds, but this change https://github.com/Katello/katello-installer/commit/b70dde1807e6b96c92d5f893d67e1172fd8a9722 (done as part of bz 1583233) actually made it run always.
Putting needinfo on Eric, as the original author of this changes.
I've updated the subject, as it was misleading, since this issue is not connected to foreman-maintain behaviour.
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, 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-2018:2927
Created attachment 1482367 [details] cli output Description of problem: Running "foreman-maintain upgrade run --target-version 6.4 -y" If "Upgrade Step: Running installer..." step fails it continues with "Upgrade Step: remove_legacy_mongo..." which resulted in breaking mongo and running "satellite-installer --upgrade" failing. When a step fails we should exit straight away Version-Release number of selected component (if applicable): 6.3.3 -> 6.4.beta upgrade.