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:

1. deploy a standalone candlepin, and configure subscription manager to use it
2. run subscription-manager-cli register
   (you now have /etc/pki/consumer/*.pem files)
3. redeploy your standalone candlepin, with FORCECERT=1
4. run subscription-manager-cli register --force
   you'll get an ssl error.

sm sees that there's a peer cert, and loads it up for use, regardless of the command running. sm should not use the cert for a register command (just like initial registration). Alternatively, sm could detect a peer verify fail, and retry without the cert.


This will happen when switching from cert-fte to standalone, too.

Potential fix sent to prad/jortel.

THis is fixed with the new secure/insecure mode.

[root@client01-rhel6-beta2 src]# ./subscription-manager-cli register --username=testuser1 --pass=password
506d9744-cf00-4717-830e-1be2193f1733 testuser1

Redeploy

[root@client01-rhel6-beta2 src]# ./subscription-manager-cli register --username=testuser1 --pass=password --force
0c1a5575-bdea-442d-8333-3241886d7ce4 testuser1
[root@client01-rhel6-beta2 src]# 

verified

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0611.html