Bug 1838382 - Satellite upgrade job failed due to "Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]}" error
Summary: Satellite upgrade job failed due to "Too many scenarios match {:tags=>[:upgra...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.8.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 6.8.0
Assignee: Suraj Patil
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-21 03:04 UTC by Devendra Singh
Modified: 2021-12-01 08:02 UTC (History)
10 users (show)

Fixed In Version: rubygem-foreman_maintain-0.6.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:38:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 29579 0 Normal Closed foreman-maintain should error if a server has both `satellite` and `satellite-capsule` packages installed. 2020-12-22 08:57:59 UTC
Red Hat Product Errata RHBA-2020:4365 0 None None None 2020-10-27 12:38:38 UTC

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
Note You need to log in before you can comment on or make changes to this bug.