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.
Bug 1712796 - Misleading error message when installed product certificates are corrupted
Summary: Misleading error message when installed product certificates are corrupted
Keywords:
Status: CLOSED DUPLICATE of bug 1971995
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: subscription-manager
Version: 8.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: candlepin-bugs
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-22 09:23 UTC by Rehana
Modified: 2022-12-12 14:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-01 07:40:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4197301 0 Troubleshoot None System Certificates Corrupted 2019-06-06 18:38:17 UTC

Description Rehana 2019-05-22 09:23:49 UTC
Description of problem:
edit /etc/pki/product-default/<pid>.pem with some junk values and try to register the system

Version-Release number of selected component (if applicable):
subscription management server: 2.7.0-1
subscription management rules: 5.37
subscription-manager: 1.25.5-1.el8

How reproducible:


Steps to Reproduce:
1.Try to register the system 
2.
3.

Actual results:
# subscription-manager register
System certificates corrupted. Please reregister.

2019-05-22 05:18:03,251 [ERROR] subscription-manager:25055:MainThread @managercli.py:519 - Error loading certificate: /etc/pki/product-default/486.pem


Expected results:
^^ notice the above message and log entry from the rhsm.log, the re-register will never work until the corrupted certificates are fixed,IMHO instead of displaying "Please reregister", link to a KBase article (if there is any ) that helps in resolving/explaining the issue will be a nice to have

Additional info:

Comment 8 RHEL Program Management 2021-02-01 07:40: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.

Comment 9 Pino Toscano 2022-12-12 14:49:31 UTC
Better error reporting for /etc/pki/product-default/*.pem files that cannot be loaded is done as part of the changes of bug 1971995.

Hence, closing this as duplicate of it.

*** This bug has been marked as a duplicate of bug 1971995 ***


Note You need to log in before you can comment on or make changes to this bug.