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.
Satellite 6.2 GA-ed today and users are unable to access the newly released 6.2 repositories that are part of their subscription:
rhel-6-server-satellite-6.2-rpms
rhel-7-server-satellite-6.2-rpms
Attempts to enable these repositories are met with errors that the repository does not exist:
# subscription-manager repos --enable rhel-7-server-satellite-6.2-rpms
Error: rhel-7-server-satellite-6.2-rpms is not a valid repository ID. Use --list option to see valid repositories.
attempts to run 'subscription-manager refresh' do not resolve the issue. The only work around is to completely un-register and re-register the system to get access to the newly released content:
WORKAROUND:
# subscription-manager identity (make note of the system id value)
# subscription-manager clean
# subscription-manager register --consumerid=<SYSTEM_IDENTITY>
# subscription-manager remove --all
# subscription-manager attach --pool=<SATELLITE_SUB_POOL>
# subscription-manager repos --enable rhel-6-server-satellite-6.2-rpms
This appears to be an issue where a product is refreshed and if only a content set is changed the entitlement for a consumer is not marked as dirty. If I manually force certificate regeneration for the consumer with the rest API it fixes the problem.
curl -s --cert /etc/pki/consumer/cert.pem --key /etc/pki/consumer/key.pem -k -X PUT https://subscription.rhn.redhat.com/subscription/consumers/<consumer_id>/certificates
(In reply to Barnaby Court from comment #1)
> This appears to be an issue where a product is refreshed and if only a
> content set is changed the entitlement for a consumer is not marked as
> dirty. If I manually force certificate regeneration for the consumer with
> the rest API it fixes the problem.
>
> curl -s --cert /etc/pki/consumer/cert.pem --key /etc/pki/consumer/key.pem
> -k -X PUT
> https://subscription.rhn.redhat.com/subscription/consumers/<consumer_id>/
> certificates
Note, the above is meant to be run on the Satellite in question. And the consumer_id is provided via 'subscription-manager identity'
An directly pasteable command is
CONSUMERID=$(subscription-manager identity | head -1 | cut -f 2 -d ":")
curl -s --cert /etc/pki/consumer/cert.pem --key /etc/pki/consumer/key.pem -k -X PUT "https://subscription.rhn.redhat.com/subscription/consumers/$CONSUMERID/certificates"
Comment 5Julio Entrena Perez
2016-07-28 08:55:35 UTC
We have modified some data in the customer portal which should refresh this issue. If you are using subscription-manager please execute the following:
subscription-manager refresh
If you are using Satellite 6, please go to
Content -> Red Hat Subscriptions -> Manage Manifest
and click the "Refresh Manifest" button
The data should now be available.
I will leave this bug open until I get customer feedback that it is fixed.
Comment 13Chris "Ceiu" Rog
2016-08-08 19:53:33 UTC
As an additional workaround/solution to the problem, subscription manager has been updated accordingly:
commit 0a2f90c86f4d7a6aec88a6fe3d3e91bbff6b2e8f
Author: Chris Rog <crog>
Date: Fri Jul 29 12:21:22 2016 -0400
1360909: The refresh command now requests entitlement cert regeneration
- When the refresh command is issued on the CLI, subman will request
entitlement certificate regeneration (lazily) for the active consumer
Moving back to on_qa as the fix in sub-man 1.17 has been taken care of and verified in test environments. I cloned to it-pnt for the portal fix to open the firewall rules to enable the updates here to work. This should be moved back to verified & released
Moving back to VERIFIED per the testing in comment 16 used to verify the developer's fix in comment 13. Note that this verification applies to the subscription-manager component changes only. Additional changes are needed server-side (by IT-Candlepin) so that a subscription-manager refresh will pick up the newly released content from the entitlement server. Per comment 31, the server-side work is now being tracked in cloned bug 1373633 where all of the external trackers have been copied to.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2592.html