Bug 1977361
| Summary: | Need to add a pre-migration check to confirm that we are on the latest 6.9.z-stream | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Ashish Humbe <ahumbe> |
| Component: | Satellite Maintain | Assignee: | Justin Sherrill <jsherril> |
| Status: | CLOSED ERRATA | QA Contact: | Gaurav Talreja <gtalreja> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.9.0 | CC: | apatel, aupadhye, desingh, jsherril, kgaikwad, rchan, zhunting |
| Target Milestone: | 6.10.0 | Keywords: | PrioBumpGSS, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | foreman-maintain-0.8.17 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-16 13:48:05 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
Ashish Humbe
2021-06-29 14:08:36 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. 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. 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. 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 Upstream bug assigned to jsherril Upstream bug assigned to jsherril 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. 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
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 |