Problem Statement

If a release version is set on the Satellite 6 server, it can cause a dependency resolution error during the Update packages step.

$ cat sos_commands/subscription_manager/subscription-manager_release_--show
Release: 9.5

Error with Satellite upgrade:

Running Migration scripts
================================================================================
Setup repositories:
/ Configuring repositories for 6.18 [OK]
--------------------------------------------------------------------------------
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)
  --------------------------------------------------------------------------------
  Scenario [Migration scripts] failed.

Business Impact

Customers are commonly using Release Version field on all their RHEL systems including Red Hat Satellite. While performing Satellite server upgrade, customers fail to unset the release version and that leads to the upgrade failure with Dependency error. To improve the user experience with upgrade, we would like to have a check in pre-upgrade steps to identify and inform customers about the release version set.