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:
If you try to unregister a system that thinks it's still registered to something, but the server doesn't recognize it anymore, you'll hit an error that says "Invalid Credentials", with a response status of 401 in rhsm.log.

As I understand it, the user's recourse in this situation is to run clean and register again if they need to. We should update the string to be something more relevant, as I initially thought the password had been changed on the account I registered the system with, not that the server didn't know who I was anymore.

Would a string like:
"Unable to unregister, the server does not recognize your system. Please run 'subscription-manager clean' to remove server information from local system."
make more sense?

Version-Release number of selected component (if applicable):
Subscription-manager-1.1.2-1.git.74.70cdd3c
python-rhsm-1.1.2-1.git.2.717d0ac

Registered to stage as stacking-stage.

Created attachment 636750 [details]
GUI Error Message

Created attachment 636751 [details]
CLI Error Message

Matt,

Let me verify that I'm following the same steps as you.

1. Register and auto-subscribe to stage.
2. Change /etc/rhsm/rhsm.conf to point to a local Candlepin installation.
3. Attempt to unregister

When I follow these steps I don't get an invalid credentials error; I actually get a "SSLError: sslv3 alert certificate unknown."  Not that the SSL error is any better, but I would like to make sure I'm doing the same thing you're doing.

Alex was never able to reproduce the message I had gotten, and I don't think I can anymore either. It seems to more normally throw out an SSL error, so if we ever tackle improvements to those (BZ 862869), that would give us a better string here.

I believe that one of you was using insecure=1, the other was using a candlepin ca cert.  Same error though, the invalid credentials for the server you are attempting to connect to.

The message has to be broad, because there are many different places that it could be raised, doing any command that interacts with the server ,not only unregister.   If the server is experiencing problems, we do not want a consumer to run subman clean, as when the server is fixed, all entitlements are gone.