Moving external from an internal ticket Subscription _"_Red Hat Update Infrastructure and RHEL Add-Ons for Providers" do not have product id 69 which is for 'Red Hat Enterprise Linux Server'. This subscription provides access to RHEL content from 'Red Hat Enterprise Linux from RHUI' repository which have product id 148 [1]. By default the installed RHEL Server OS will have product certificate 69.pem for 'Red Hat Enterprise Linux Server'. When using this system for RHUI installation and attaching RHUI subscription to it, it is able to get base-os contents from "RHEL from RHUI" repo but the subscription-manager and the system profile on customer portal shows its subscription status as invalid. Which is expected because the attached RHUI [2] subscription do not cover product id 69. There is no product certificate for id 148. RPM subscription-manager-migration-data too do not have any such product certificate. Once the system is registered as RHUI, it is not possible to attach any other subscription to it which covers product id 69[3]. Either need to update the "Red Hat Update Infrastructure" subscription certificate with 69 product id or need to provide product certificate 148.pem [1] https://access.redhat.com/management/subscriptions/product/RC1116415/content?product_id=148 [2] https://access.redhat.com/management/subscriptions/product/RC1116415 [3] https://access.redhat.com/management/subscriptions/product/RC1257407/content?product_id=69 Version-Release number of selected component (if applicable) Steps to Reproduce: Register system as RHUI with RHSM using subscription-manager _Attach "_Red Hat Update Infrastructure and RHEL Add-Ons for Providers" subscription to system. From customer portal check system status. Also use 'subscription-manager status' to check status from system terminal. Actual results: Subscription status shows invalid. Expected results: subscription-manager status and profile on portal should show subscription status as valid.
Hello Team, This still is still present in RHUA 4.
This is not something to be addressed by RHUI. RHUI does have product id 69 already it's just in a different form that includes */rhui/* in the repo path. If we added product id 60 it would cripple RHUI installs across hundreds of partners. If there is a product out there that requires that product id 69 be available, I would like to meet with them to help them better understand why this is not a possibility or at least understand why they think breaking RHUI would solve their problem while something simple is looking right at them: the content is already there, it's just not labeled as product id 69.