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.

I just repeated it to be sure: I went to the web interface kingpin -> Consumers and removed my system, then I fired up the RHSM gui and it says 'Unregister System'.  I clicked the unregister button and got the error here:
http://file.rdu.redhat.com/~jbastian/entitlement/rhsm-unregister.png

I closed the RHSM gui tool, restarted it, and it still says Unregister System.

Cannot reproduce in standalone, was trying to do so by using curl to delete the consumer in candlepin, which should be sufficient to trigger this. The error pops up, but the GUI button switches straight to "Register System". On restart it remains "Register System".

Dug through the code and I can't see how this would happen, the cert deletion is in a finally block which should clean them out even when the auth fails. (which is expected in this scenario)

I attempted to test directly against kingpin but I'm told using the test accounts could pose problems for QE. Have strong suspicion the standalone test steps above should cover it anyhow.

So, possible this has since been fixed? Anyone able to reproduce today?

what error do you get?

I get the error in the screenshot, this is expected behavior I think. (the consumer has been deleted, his identity cert is no longer valid to authenticate with, but the client has no way to know this)

The part with unregister however should clean up those certs and after that, the client should think it's unregistered, even if the auth fails when trying to unregister. That part is what I assumed this bug was about, but I cannot reproduce.

ok... I am fine with that.