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 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 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
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 ***