Bug 752165

Summary:	rhn-channel --add --channel=rhel-x86_64-server-optional-6 fails with error 37
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Kurt Seifried <kseifried>
Component:	aeolus-all	Assignee:	Mike Orazi <morazi>
Status:	CLOSED NOTABUG	QA Contact:	wes hayutin <whayutin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0.0	CC:	gszasz, jlaska
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-10 15:56:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Kurt Seifried 2011-11-08 17:45:21 UTC

Description of problem:

I have a fresh RHEL 6.1 install, registered, yum update'd. I follow the instructions at http://aeolusproject.org/get_it.html

# rhn-channel --add --channel=rhel-x86_64-server-optional-6

and get the error:

Error communicating with server. The message was:

Error Class Code: 37
Error Class Info: You are not allowed to perform administrative tasks              on this system.
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.

which gives 2 results in google.

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

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.1 (Santiago)


How reproducible:

always

Steps to Reproduce:
1. install rhel 6.1
2. register and update
3. run rhn-channel --add --channel=rhel-x86_64-server-optional-6
  
Actual results:


Expected results:


Additional info:

I am told this may be related to permissions in my RHN account, but I really have no idea how to check them.verify this.

Comment 1 Mike Orazi 2011-11-30 20:22:47 UTC

Kurt,

My rhn knowledge is a little dated, but the best guess I can give is that the user account you used to register this does not have permissions to actually manage the system in question.  Easiest thing is probably to follow up with the person who created your rhn account and make sure your account has permission to manage system via system group associations.

Comment 2 wes hayutin 2011-12-10 15:56:04 UTC

not a ce issue

Comment 3 Kurt Seifried 2012-02-23 06:53:39 UTC

Correct, it's an RHN permissions issue. You need admin/manage control over systems you register or else you get this error 37. Contact GSS to get your account permissions set for this.