Bug 1838382

Summary: Satellite upgrade job failed due to "Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]}" error
Product: Red Hat Satellite Reporter: Devendra Singh <desingh>
Component: Satellite MaintainAssignee: Suraj Patil <supatil>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: high    
Version: 6.8.0CC: apatel, egolov, gtalreja, jyejare, kgaikwad, pcreech, supatil, vijsingh, vsedmik, zhunting
Target Milestone: 6.8.0Keywords: AutomationBlocker, Triaged, UpgradeBlocker, Upgrades
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.6.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:38:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Devendra Singh 2020-05-21 03:04:23 UTC
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

Comment 2 Suraj Patil 2020-05-27 15:39:39 UTC
@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.

Comment 3 Devendra Singh 2020-05-28 11:49:23 UTC
(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.

Comment 8 Kavita 2020-06-05 08:19:40 UTC
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!

Comment 9 Bryan Kearney 2020-06-11 16:01:44 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29579 has been resolved.

Comment 13 errata-xmlrpc 2020-10-27 12:38:24 UTC
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