-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
3
-
False
-
Satellite Rocket Sprint 13, Satellite Rocket Sprint 12
-
sat-rocket
-
None
-
None
-
None
-
None
Installing Satellite is only supported on "latest RHEL", but users often limit their systems to a specific X.Y release by using subscription-manager release --set X.Y.
This results in an unsupported setup and can lead to dependency issues during installation and upgrade:
Download package(s) : [FAIL] Failed executing dnf -y --downloadonly --disableplugin=foreman-protector update, exit status 1: Updating Subscription Management repositories. This system has release set to 9.5 and it receives updates only for this release. Red Hat Enterprise Linux 9 for x86_64 - BaseOS 35 MB/s | 54 MB 00:01 Red Hat Enterprise Linux 9 for x86_64 - AppStre 33 MB/s | 55 MB 00:01 Red Hat Satellite Maintenance 6.18 for RHEL 9 x 56 kB/s | 37 kB 00:00 Red Hat Satellite 6.18 for RHEL 9 x86_64 (RPMs) 842 kB/s | 920 kB 00:01 Error: Problem: cannot install the best update candidate for package pulpcore-selinux-2.0.1-1.el9pc.x86_64 - nothing provides selinux-policy >= 38.1.53-5.el9_6 needed by pulpcore-selinux-2.1.0-1.el9pc.x86_64 from satellite-6.18-for-rhel-9-x86_64-rpms (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Provide a foreman_maintain check to inform the users they are running an unsupported setup and should unset the release before performing the upgrade.
Acceptance criteria:
- A check for subscription-manager release exists
- The check is automatically executed on every update and upgrade
Open questions:
- The same issue can happen during initial installation, but there we have no f-maintain to perform checks. Should we do anything in this case?
- is depended on by
-
SAT-40180 [RFE] - Include a release version set check step during the upgrade process.
-
- New
-
