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:
Similar to prior bug 1704953, we have the same failures for satellite 6.6 eus....
----------------------------------------------------------------------------------------------------------------------
Engineering product 292 - "Red Hat Enterprise Linux for Power, little endian - Extended Update Support" provides access to the following content sets...
ContentSetLabel ContentSetID ActualModifiedEngIDs ExpectedModifiedEngIDs
rhel-7-for-power-le-eus-satellite-tools-6.6-debug-rpms 8967 [] <= FAILED 279
rhel-7-for-power-le-eus-satellite-tools-6.6-rpms 8968 [] <= FAILED 279
rhel-7-for-power-le-eus-satellite-tools-6.6-source-rpms 8969 [] <= FAILED 279
----------------------------------------------------------------------------------------------------------------------
Engineering product 70 - "Red Hat Enterprise Linux Server - Extended Update Support" provides access to the following content sets...
ContentSetLabel ContentSetID ActualModifiedEngIDs ExpectedModifiedEngIDs
rhel-7-server-eus-satellite-tools-6.6-debug-rpms 8937 [] <= FAILED 69
rhel-7-server-eus-satellite-tools-6.6-rpms 8938 [] <= FAILED 69
rhel-7-server-eus-satellite-tools-6.6-source-rpms 8939 [] <= FAILED 69
----------------------------------------------------------------------------------------------------------------------
Engineering product 75 - "Red Hat Enterprise Linux for Power, big endian - Extended Update Support" provides access to the following content sets...
ContentSetLabel ContentSetID ActualModifiedEngIDs ExpectedModifiedEngIDs
rhel-7-for-power-eus-satellite-tools-6.6-debug-rpms 8961 [] <= FAILED 74
rhel-7-for-power-eus-satellite-tools-6.6-rpms 8962 [] <= FAILED 74
rhel-7-for-power-eus-satellite-tools-6.6-source-rpms 8963 [] <= FAILED 74
----------------------------------------------------------------------------------------------------------------------
Because these are EUS content sets, the intended business requirement is that a customer who is granted an entitlement to these content sets must also have an entitlement to the base product that these EUS content sets modify. In order to achieve this requirement, the RHSM Candlepin tooling expects the list of ModifiedEngIDs to be accurate and non-empty. If product management agrees, then I believe the following rcm file
http://git.app.eng.bos.redhat.com/git/rcm/rcm-metadata.git/tree/cdn/cs_mappings-prod.csv
should be updated to include an ENG CONTENT ID, MODIFIES mapping to the product ExpectedModifiedEngIDs listed in the table above.
If no changes are made, then a customer will continue gaining access to the EUS content provided by the failing repos above without also attaching an entitlement that provides the base engineering id.
Comment 10RHEL Program Management
2021-03-15 07:37:58 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.