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.
At the moment, it's possible to end up in the middle of upgrade and
the upgrade prevent the user to specify different `--target-version`.
Steps to reproduce:
1. foreman-maintain upgrade run --target-version 6.2.z
2. simulate it failed in the migration phase
3. foreman-maintain upgrade --target-version 6.3
Current results:
The second upgrade scenario starts without issues.
Related issue to this is, when the upgrade fails at the installer run phase, the list of available versions
is already updated to the next versions, making it impossible to continue with the upgrade.
Expected results:
The upgrade to 6.3 will fail because another upgrade is already in progress
VERIFIED
Version Tested:
# rpm -q rubygem-foreman_maintain
rubygem-foreman_maintain-0.1.1-1.el7sat.noarch
Steps:
# foreman-maintain upgrade run --target-version 6.2.z
# manage to fail upgrade run in packages-update
# foreman-maintain upgrade run --target-version 6.3
Can't set target version 6.3, 6.2.z already in progress
Comment 6sthirugn@redhat.com
2018-02-16 14:34:00 UTC
Closed as a duplicate of BZ 1487539. Both bugs have the same description, but the other bug has more detailed verification steps.
*** This bug has been marked as a duplicate of bug 1487539 ***