1977361 – Need to add a pre-migration check to confirm that we are on the latest 6.9.z-stream

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 1977361 - Need to add a pre-migration check to confirm that we are on the latest 6.9.z-stream

Summary: Need to add a pre-migration check to confirm that we are on the latest 6.9.z-...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Satellite Maintain
Sub Component:
Version:	6.9.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	urgent
Severity:	high
Target Milestone:	6.10.0
Assignee:	Justin Sherrill
QA Contact:	Gaurav Talreja
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2021-06-29 14:08 UTC by Ashish Humbe
Modified:	2021-11-16 13:48 UTC (History)
CC List:	7 users (show)
Fixed In Version:	foreman-maintain-0.8.17
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2021-11-16 13:48:05 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	33406	0	Normal	Closed	add z-stream check & question for 6.10 upgrades	2021-09-23 14:19:53 UTC
Red Hat Product Errata	RHBA-2021:4697	0	None	None	None	2021-11-16 13:48:12 UTC

Description Ashish Humbe 2021-06-29 14:08:36 UTC

Description of problem:

We are shipping the latest pulp2-pulp3 migration fixes in 6.9.z and as per the current upgrade policy we do not force customers to be on the latest z-stream before upgrading to the next major version. I think for Sat6.10 we need to change this and customers need to have the latest pulp2-pulp3 migration fixes installed. 

Need to add a pre-migration check to confirm that we are on the latest 6.9.z-stream before starting the migration to Pulp3. May be as part of the "satellite-maintain prep-6.10-upgrade " command.

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

Comment 2 Justin Sherrill 2021-08-03 18:20:59 UTC

The only way to ensure that the user is on the latest is to release a new version of foreman-maintain that an explicit check for the latest package version with each 6.9.z release.  I'm not sure we want to do that, so the best we can do is either:

1) prompt the user to ensure they are on the latest and only continue if they say yes
2) check that there is no update available for the tfm-rubygem-katello or foreman-maintain packages  and ask the user to upgrade if there is a newer package available.  This wouldn't really help at all with disconnected satellites though, as they likely won't have an upgraded package available via yum.

Comment 3 Robin Chan 2021-08-03 20:33:03 UTC

I'm also concerned about hard coding or retrieving the "latest" 6.9.z release (needing to force an override in case connection is not available.) I question the value of coding a message to tell users to check, but understand talking about it too much will also not be valuable.

Comment 4 Ashish Humbe 2021-08-04 10:08:45 UTC

Thank you Justin, Robin for sharing your thoughts on this.

I think after discussion with Brad and Mike, the main idea behind this RFE was that we are releasing pulp3 updates in each 6.9.z which includes bugfixes and if customers are not using the latest pulp3 packages then they might hit some known issues and that will lead to increased support case volume and bad upgrade experience for the customer. Till now we are allowing customers to upgrade to the latest major version from any minor version of the earlier release, ie: customers can upgrade to Satellite 6.9 from 6.8.1 also and the upgrade works well. 

So when customers run "satellite-maintain prep-6.10-upgrade " we should have an easy way to confirm that they are using the packages that provide latest Pulp2-Pulp3 migration fixes. 




1) prompt the user to ensure they are on the latest and only continue if they say yes
>> It will be difficult for customers to confirm that they are using the latest 6.9 z-stream updates or not.

Should we run " satellite-maintain upgrade run --target-version 6.9.z " as part of "satellite-maintain prep-6.10-upgrade " or any other step or add this step the upgrade documentation guide?

2) check that there is no update available for the tfm-rubygem-katello or foreman-maintain packages  and ask the user to upgrade if there is a newer package available.  This wouldn't really help at all with disconnected satellites though, as they likely won't have an upgraded package available via yum.
>> I understand that it will be difficult to add a check for foreman_maintain package version.

Comment 5 Justin Sherrill 2021-08-24 18:01:22 UTC

I think we can use 'yum check-update' to see if any update is available as part of 'foreman-maintain upgrade run'  we just have to do that with the packages unlocked

Comment 7 Bryan Kearney 2021-09-03 00:05:22 UTC

Upstream bug assigned to jsherril

Comment 8 Bryan Kearney 2021-09-03 00:05:24 UTC

Upstream bug assigned to jsherril

Comment 10 Justin Sherrill 2021-09-23 12:43:27 UTC

Hey Devendra, 

It looks like you've got a newer version of katello or the migration plugin available for upgrade.  If you've already enabled the 6.10 repo on that box, you may have to whitelist that check.

Comment 15 Gaurav Talreja 2021-10-13 12:58:34 UTC

Verified.

Tested on Satellite 6.9.6 or any older 
Version: rubygem-foreman_maintain-0.8.19-1.el7sat.noarch (From Satellite 6.10.0 Snap 22)

Setup:
1. Configure/enable latest z-stream repos from dogfood/CDN.
2. Make sure updates are available for tfm-rubygem-katello, python3-pulp-2to3-migration packages, with
    # foreman-maintain packages check-update

Steps:
1. # foreman-maintain upgrade check --target-version=6.10 --whitelist="repositories-validate"

Observation:
If updates are available for tfm-rubygem-katello, python3-pulp-2to3-migration from latest z-stream repos, then upgrade check fails and asks the user to update before proceeding with the upgrade.

While updating those packages installer fails, raised a bug[1] for that against an installer.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2013641

Comment 18 errata-xmlrpc 2021-11-16 13:48:05 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.10 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-2021:4697

Note You need to log in before you can comment on or make changes to this bug.