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 1136842 - error with yum install
Summary: error with yum install
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.0
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: pre-dev-freeze
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel67
TreeView+ depends on / blocked
 
Reported: 2014-09-03 12:13 UTC by eric.letourneur
Modified: 2015-05-15 19:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-21 18:38:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description eric.letourneur 2014-09-03 12:13:06 UTC 
Description of problem:

I want to migrate from Basic RHN Classic to Customer Portal Subscription Management. I follow instructions with command yum install on root :

[root@KMCHMORA002 ~]# yum install subscription-manager-migration subscription-manager-migration-data
Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Il y a eu une erreur de communication avec RHN.
Le support de RHN Satellite ou RHN Classic sera désactivé.

Message d'erreur :
	Veuillez exécuter rhn_register en tant que root sur ce client
Error Class Code: 9
Error Class Info: Invalid System Credentials.
Explanation: 
     An error has occurred while processing your request. If this problem
     persists please enter a bug report at bugzilla.redhat.com.
     If you choose to submit the bug report, please be sure to include
     details of what you were trying to do when this error occurred and
     details on how to reproduce this problem.

Setting up Install Process
No package subscription-manager-migration available.
No package subscription-manager-migration-data available.
Error: Nothing to do



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

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
Message d'erreur :
	Veuillez exécuter rhn_register en tant que root sur ce client
Error Class Code: 9
Error Class Info: Invalid System Credentials.

Expected results:
Installation OK

Additional info:
I'm already root when i execute command yum.
Comment 1 Bryan Kearney 2014-09-12 15:56:33 UTC 
Are you registered with rhn currently?
Comment 2 eric.letourneur 2014-09-17 14:10:35 UTC 
Hello

Is anyone have an idea to solve this error ?

Thanks
Eric
Comment 3 John Sefler 2014-09-17 22:05:04 UTC 
The message "Il y a eu une erreur de communication avec RHN" seems to indicate that there was an error while communicating with RHN.  My guess is that something is poorly configured in /etc/sysconfig/rhn/up2date which is owned by the rhn-client-tools package/component.

At this point (in comment 0), you have not yet touched the subscription-manager component tools.

I am also curious what the answer is to comment 1.
What does "rhn-channel --list" report?
Comment 4 eric.letourneur 2014-09-18 07:38:47 UTC 
Thanks for your answer. My problem is solved. The server wasn't licenced in the classic subscription. I passed the licenced and i have migrated with success.

Regards,
Eric
Comment 5 Devan Goodwin 2014-11-21 18:38:00 UTC 
Closing per comment #4, thanks for the response.
Note You need to log in before you can comment on or make changes to this bug.