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:
There is a satellite server which was upgraded to sat 6.3 using foreman-maintain.

If you run command again - foreman-maintain upgrade run
Output:
  Could not find scenario satellite_6_3_pre_upgrade_check, found 0 scenarios


Version-Release number of selected component (if applicable):
rubygem-foreman_maintain-0.0.10-1.el7sat.noarch

How reproducible:


Steps to Reproduce:
1. Start upgrading satellite server to sat 6.3 using foreman-maintain
2. In case satellite-installer failed due to some reason, try to re-run below command -
foreman-maintain upgrade run
3. It gives error for scenario

Actual results:
Could not find scenario satellite_6_3_pre_upgrade_check, found 0 scenarios


Expected results:
It should continue with upgrading process where it failed previously.

Additional info:

*** Bug 1508349 has been marked as a duplicate of this bug. ***

Fixed in foreman-maintain-0.0.11,
https://github.com/theforeman/foreman-packaging/pull/1909

Verified in rubygem-foreman_maintain-0.0.11-1.el7sat.noarch.

Successfully cloned a db using clone tool, upgraded with rubygem-foreman_maintain.

After upgrading to 6.3 beta:

# foreman-maintain upgrade run --target-version 6.3
Can't upgrade to 6.3
Possible target versions are:
6.3.z

# foreman-maintain upgrade check
--target-version not specified
Possible target versions are:
6.3.z

*** Bug 1512464 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/RHEA-2017:3192