Hide Forgot
See Katello BZ (https://bugzilla.redhat.com/show_bug.cgi?id=736482) When providing invalid credentials while system registration using subscription-manager against katello, there is an error: ERROR: Server does not support environments. Expected result: Invalid Credentials The problem is, subscription-manager tries to find out whether server supports environments, but doesn't checks if the request to katello was successful (katello returns 401 Unauthorized).
Verifying Version.... candlepin-0.5.26-1.el6.noarch katello-0.1.304-1.el6.noarch [root@ibm-ls22-04 ~]# rpm -q subscription-manager subscription-manager-0.99.10-1.el6.x86_64 [root@ibm-ls22-04 ~]# subscription-manager orgs --username admin --password BAD Invalid credentials [root@ibm-ls22-04 ~]# subscription-manager orgs --username admin Password: +-------------------------------------------+ admin Organizations +-------------------------------------------+ Name: ACME_Corporation Key: ACME_Corporation Name: bbbbb Key: bbbbb [root@ibm-ls22-04 ~]# subscription-manager environments --org ACME_Corporation --username admin --password BAD Invalid credentials [root@ibm-ls22-04 ~]# subscription-manager environments --org ACME_Corporation --username admin Password: +-------------------------------------------+ Environments +-------------------------------------------+ Name: Library Description: None Name: dev Description: Name: qae Description: Name: e2e Description: [root@ibm-ls22-04 ~]# subscription-manager register --org ACME_Corporation --environment dev --username admin --password BAD Invalid credentials [root@ibm-ls22-04 ~]# subscription-manager register --org ACME_Corporation --environment dev --username admin Password: The system has been registered with id: 891b996c-2191-44aa-bd92-93659b4dd6ef [root@ibm-ls22-04 ~]# ^^ VERIFIED: "Invalid Credentials" was given as feedback for subscription-manager modules orgs, environments, and register each time a BAD password was given. moving to 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. http://rhn.redhat.com/errata/RHBA-2012-0804.html