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.
Description of problem: Satellite upgrade job failed due to "Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]}" error
Version-Release number of selected component (if applicable):
6.8
How reproducible:
always
Steps to Reproduce:
1. Perform the satellite upgrade from 6.7 to 6.8.0 using foreman-maintain.
2. Upgrade job failed with an error like "Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]}"
#foreman-maintain upgrade run --whitelist="disk-performance" --target-version 6.8 -y
Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]}
Actual results:
Satellite upgrade failed.
Expected results:
Satellite upgrade should be completed successfully.
Additional info: Used foreman-maintain package version: 0.6.3
@Devendra It seems that you have both satellite and satellite-capsule package installed on satellite server. Can you please verify it?
Try removing the satellite-capsule package(#yum remove satellite-capsule) if installed and then try to upgrade again.
(In reply to Suraj Patil from comment #2)
> @Devendra It seems that you have both satellite and satellite-capsule
> package installed on satellite server. Can you please verify it?
> Try removing the satellite-capsule package(#yum remove satellite-capsule) if
> installed and then try to upgrade again.
yes, both packages were available, I removed the satellite-capsule package and re-execute the command again but this time didn't see the problem.
Hello,
For removal of "satellite-capsule" package, created BZ under Packaging component - https://bugzilla.redhat.com/show_bug.cgi?id=1844344
This BZ will only take care of foreman-maintain side change in the Capsule feature.
Thanks!
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 (Satellite 6.8 Satellite Maintenance Release), 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-2020:4365
Description of problem: Satellite upgrade job failed due to "Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]}" error Version-Release number of selected component (if applicable): 6.8 How reproducible: always Steps to Reproduce: 1. Perform the satellite upgrade from 6.7 to 6.8.0 using foreman-maintain. 2. Upgrade job failed with an error like "Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]}" #foreman-maintain upgrade run --whitelist="disk-performance" --target-version 6.8 -y Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]} Actual results: Satellite upgrade failed. Expected results: Satellite upgrade should be completed successfully. Additional info: Used foreman-maintain package version: 0.6.3