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.

Bug 2106333

Summary:	Add Satellite and Capsule 6.12 upgrade scenarios
Product:	Red Hat Satellite	Reporter:	Amit Upadhye <aupadhye>
Component:	Satellite Maintain	Assignee:	Amit Upadhye <aupadhye>
Status:	CLOSED ERRATA	QA Contact:	Gaurav Talreja <gtalreja>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.12.0	CC:	apatel, kgaikwad, swadeley, zhunting
Target Milestone:	6.12.0	Keywords:	Triaged, UpgradeBlocker, Upgrades
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	rubygem-foreman_maintain-1.1.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-16 13:34:34 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 Amit Upadhye 2022-07-12 11:43:43 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Amit Upadhye 2022-07-12 11:48:20 UTC

Created redmine issue https://projects.theforeman.org/issues/35201 from this bug

Comment 2 Gaurav Talreja 2022-07-18 11:19:43 UTC

Hello,

There is a wrong version of rubygem-foreman_maintain in 6.12 snap2 (which comes from 6.11.1 snap2), could you please check?

Thanks
Gaurav

Comment 3 Gaurav Talreja 2022-07-29 08:01:09 UTC

Hi,

While testing upgrades with rubygem-foreman_maintain-1.1.4-1.el8sat.noarch, upgrades to 6.12.0 to 6.12.z succeeded for Satellite and Capsule, and upgrades from 6.11.z to 6.12.0 also passed for Satellite but failed for Capsule, with this error in the list-versions command,

# foreman-maintain upgrade list-versions
No such file or directory @ rb_check_realpath_internal - /etc/foreman-installer/scenarios.d/last_scenario.yaml

Therefore, I am moving this BZ back to the ASSIGNED state. Please feel free to update it as needed.


Thanks
Gaurav

Comment 4 Amit Upadhye 2022-08-16 14:06:35 UTC

Hello,

I am setting this back to ON_QA as we don't expecting missing the last_scenario.yaml in working state of Satellite or Capsule systems.

@Gaurav request you to move it to verified state once you are done with any of the pending tests you may be working on.

Regards,
Amit Upadhye.

Comment 5 Gaurav Talreja 2022-08-26 13:13:18 UTC

Verified.
Tested on Satellite 6.12.0 Snap 8.0
Version: rubygem-foreman_maintain-1.1.4-1.el8sat.noarch

Steps:
1. # foreman-maintain upgrade run --target-version 6.12 --whitelist 'repositories-validate,repositories-setup'

Observation:
Tested both Satellite and Capsule upgrades from 6.11.z to 6.12 and 6.12.0 to 6.12.z

Comment 9 errata-xmlrpc 2022-11-16 13:34:34 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 (Important: Satellite 6.12 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/RHSA-2022:8506