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.
Bug 1310454 - subscription-manager list --available comes back with this error message "Invalid credentials.'
Summary: subscription-manager list --available comes back with this error message "Inv...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.1
Hardware: ppc64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-21 19:31 UTC by Claude Dube
Modified: 2016-02-22 16:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-22 16:57:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
subscription-manager's log file (187.11 KB, text/plain)
2016-02-21 19:31 UTC, Claude Dube
no flags Details

Description Claude Dube 2016-02-21 19:31:40 UTC
Created attachment 1129075 [details]
subscription-manager's log file

Description of problem:
Login as root on client the subscription-manager has been successfully registered. however, subscription-manager list --available comes out with this error message "Invalid credentials."

The system time is perfectly synchronized.

Version-Release number of selected component (if applicable):

rpm -qa | egrep "subscription-manager|python-rhsm"
python-rhsm-1.13.10-1.el7.ppc64
subscription-manager-1.13.22-1.el7.ppc64

subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.51.11-1
subscription management rules: 5.15
subscription-manager: 1.13.22-1.el7
python-rhsm: 1.13.10-1.el7


How reproducible:
always


Steps to Reproduce:
1. subscription-manager list --available
   Invalid credentials.

2.
3.

Actual results:
"Invalid credentials.'

Expected results:
returns repository list

Additional info:

Comment 2 Barnaby Court 2016-02-22 16:57:20 UTC
This appears to be a configuration issue:

Looking the log file it appears that the consumer identity certificate has been removed. 

2016-02-21 12:53:53,374 [DEBUG] subscription-manager @identity.py:143 - Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such file or directory: '/etc/pki/consumer/key.pem'


This would usually be the case if a system has either never been registered or was unregistered. 

This can be validated by running "subscription-manager identity". If the consumer has been properly registered please re-open and attach the archive generated by "rhsm-debug system"


Note You need to log in before you can comment on or make changes to this bug.