RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Description of problem:
With specific release "7.4" of subscription-manager, it failed to update because following version of packages are not in the repository.

- selinux-policy-base
- selinux-policy
- selinux-policy-targeted

version: 3.13.1-192.el7_5.3 

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


How reproducible:


Steps to Reproduce:
1.subscription-manager release --set 7.4
2.yum clean all; yum repolist
3.yum update

Actual results:

dependencies errors
~~~
Error: Package: 2:container-selinux-2.55-1.el7.noarch (rhel-7-server-extras-rpms)
           Requires: selinux-policy >= 3.13.1-183
           Removing: selinux-policy-3.13.1-102.el7.noarch (@anaconda/7.3)
               selinux-policy = 3.13.1-102.el7
           Updated By: selinux-policy-3.13.1-166.el7_4.9.noarch (rhel-7-server-rpms)
               selinux-policy = 3.13.1-166.el7_4.9
           Available: selinux-policy-3.12.1-153.el7.noarch (rhel-7-server-rpms)
...
..
~~~

Expected results:
No errors.

Additional info:

This is not a bug.

Error: Package: 2:container-selinux-2.55-1.el7.noarch (rhel-7-server-extras-rpms)

This package is only available in rhel-extras.
If you are using items in extras, you are expected to be on the latest release, per: https://access.redhat.com/support/policy/updates/extras/

You could use an unsupported solution of version locking packages to get your updates to continue, or perhaps a repo-override via subscription-manager to point extras at the 7.4 tree (which does exist, but is not configurable via release within sub-man/entitlements).

In particular it's not a bug in the rpm software, which is what the component "rpm" is about. As a general rule: if in doubt, problems concerning package X should be filed on component X.


Like Craig pointed out, Extras policy is what it is, so this is hardly a bug.