Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Content sets for ELS (Red Hat Enterprise Linux Extended Life Cycle) should have a cs_mapping constraint similar to EUS that enforces RHEL systems to be entitled to the base RHEL products in addition to the ELS add-on subscription support. (inferred from https://access.redhat.com/solutions/690063 "...We require that customers running Red Hat Enterprise Linux products beyond their retirement continue to have active subscriptions which ensures that they continue receiving access to all previously released content, ..."). That means that content set constraints should be imposed on all *-els-* content set repos that will block an entitled rhel system from accessing the *-els-* repos until they have also attached a subscription that provides the base rhel engineering product that the *-els-* repos extend. To achieve this behavior, the OIDS for all *-els-* content set repos need to be added to a cs_mappings file followed by a call to refresh pools for all the ELS engineering ids.
Below are lists of the ELS content set OIDs missing from...
http://git.app.eng.bos.redhat.com/git/rcm/rcm-metadata.git/tree/cdn/cs_mappings-prod.csvhttp://git.app.eng.bos.redhat.com/git/rcm/rcm-metadata.git/tree/cdn/cs_mappings-stage.csvhttp://git.app.eng.bos.redhat.com/git/rcm/rcm-metadata.git/tree/cdn/cs_mappings-qa.csv
----------------------------------------------------------
From EngID 204: Red Hat Enterprise Linux Server - Extended Life Cycle Support
Provided by add-on sku RH00270: Red Hat Enterprise Linux Extended Life Cycle Support (Physical or Virtual Nodes)
The ENG CONTENT IDs below correspond to rhel-6-server-els-* content set repos and should extend the rhel-6-server-* content set repos provided by EngID 69.
ENG CONTENT ID, MODIFIES Content Set Label provided for information
7396, 69 <==== rhel-6-server-els-rpms
7397, 69 <==== rhel-6-server-els-debug-rpms
7399, 69 <==== rhel-6-server-els-source-rpms
7408, 69 <==== rhel-6-server-els-optional-rpms
7409, 69 <==== rhel-6-server-els-optional-debug-rpms
7411, 69 <==== rhel-6-server-els-optional-source-rpms