Red Hat Bugzilla – Bug 848742
Certification file name is incorrect when doing auto-subscribe on RHEL 5.9 client/server i386
Last modified: 2013-01-10 06:03:30 EST
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
I have also checked against the RHEL 5.9 Server with the same build, but the issue dose NOT happen.
I have double-checked this issue again and find this bug also can just be reproduced on RHEL 5.9 Server i386 and RHEL 5.9 Client i386, but it does NOT happen to RHEL 5.9 Server x86_64 and RHEL 5.9 Client x86_64, so I doubt it is related to arch and it's a i386 special issue.
Are the certs that got written as the -1-key.pem/-1-cert.pem available?
(In reply to comment #4)
> Are the certs that got written as the -1-key.pem/-1-cert.pem available?
The certs are not available. It can not unsubscribe in GUI. Following error dialog show up: "Entitlement Certificate with serial number -1 could not be found." But with command "subscription-manager unsubscribe --all", I can unsubscribe.
Attached the cert files
Created attachment 606435 [details]
Created attachment 606436 [details]
cert file 2
Failed to upload cert file "-1-key.pem" directly, so I compressed it. please decompress it with command "tar -zxvf key2.tar.gz"
Created attachment 606437 [details]
This bug is always blocking the Alpha build test, would you pls help take a look and resolve the issue asap? Thanks!
fixed in master, 09e8c89c4ab865f
should be in python-rhsm 1.0.6
This bug has been verfied and passed on 5.9 client 386
This bug has been verfied and passed with python-rhsm-1.0.6-1.el5 on RHEL 5.9 client i386.
On RHEL 5.9 client i386 with python-rhsm-1.0.6-1.el5, verified the issue as per the above steps and can get cert files with correct name under /etc/pki/entitlement/ as below:
So marked this bug status as verified.
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.