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
Created from redmine issue http://projects.theforeman.org/issues/20597
Upstream bug assigned to None
Upstream bug assigned to inecas
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20597 has been resolved.
VERIFIED Version Tested: # rpm -q rubygem-foreman_maintain rubygem-foreman_maintain-0.1.1-1.el7sat.noarch Trying to upgrade from 6.1 to 6.2 # foreman-maintain upgrade run --target-version 6.2 Managed to fail upgrade in migration # foreman-maintain upgrade run --target-version 6.3 Can't set target version 6.3, 6.2 already in progress Also while verifying https://bugzilla.redhat.com/show_bug.cgi?id=1487538, tried to upgrade from 6.2 to 6.2.z # foreman-maintain upgrade run --target-version 6.2.z managed to fail upgrade run # foreman-maintain upgrade run --target-version 6.3 Can't set target version 6.3, 6.2.z already in progress
*** Bug 1487538 has been marked as a duplicate of this bug. ***
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/RHBA-2018:0330