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:
As fixed in the original bug 1414529 , the rhsm.log now displays the corrupted product id file in the rhsm.log Ex: Error loading certificate: /etc/pki/product/37060.pem . However if the system had multiple corrupted files user needs to fix the product cert one by one as the rhsm.log doesn't list all the corrupted files in one shot.
Version-Release number of selected component (if applicable):
subscription-manager: 1.20.2-1.el7
python-rhsm: 1.20.2-1.el7
How reproducible:
always
Steps to Reproduce:
1.Modify few product certs with junk values
[root@hp-sl4545g7-01 ~]# rct cc /etc/pki/product/37060.pem
Unable to read certificate file '/etc/pki/product/37060.pem': Error loading certificate: /etc/pki/product/37060.pem
[root@hp-sl4545g7-01 ~]# rct cc /etc/pki/product-default/69.pem
Unable to read certificate file '/etc/pki/product-default/69.pem': Error loading certificate: /etc/pki/product-default/69.pem
2.execute `subscription-manager list --installed`
[root@hp-sl4545g7-01 ~]# subscription-manager list --installed
System certificates corrupted. Please reregister.
Actual results:
Observed that rhsm.log only mentioned one corrupted product id file
Expected results:
User needs to fix the product id one by one as the corrupted product id files are not listed at once. It will be good to list all the corrupted product id files in the rhsm.log
Additional info:
rhsm.log
2017-10-27 05:14:24,283 [INFO] subscription-manager:10824:MainThread @managercli.py:453 - X-Correlation-ID: 5c39132dbb0a4545ac35da522d73a27f
2017-10-27 05:14:24,283 [INFO] subscription-manager:10824:MainThread @managercli.py:342 - Client Versions: {'python-rhsm': '1.20.2-1.el7', 'subscription-manager': '1.20.2-1.el7'}
2017-10-27 05:14:24,285 [INFO] subscription-manager:10824:MainThread @connection.py:832 - Connection built: host=subscription.rhsm.stage.redhat.com port=443 handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=False
2017-10-27 05:14:24,286 [INFO] subscription-manager:10824:MainThread @connection.py:832 - Connection built: host=subscription.rhsm.stage.redhat.com port=443 handler=/subscription auth=none
2017-10-27 05:14:24,305 [ERROR] subscription-manager:10824:MainThread @managercli.py:506 - Error loading certificate: /etc/pki/product/37060.pem
Stale Bug Clean up :
Thank you for opening the bug . The scenario is described above is not a common scenario to experience for the customer. With our current priority of the backlog we will not be able to work on this request.
Hence closing this bug as part of stale bug policy review and clean up .
thanks ,
Rehana