Bug 470336

Summary:	user.setDefaultSystemGroup only accepts groups that the user is subscribed to
Product:	Red Hat Satellite 5	Reporter:	Justin Sherrill <jsherril>
Component:	API	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED CURRENTRELEASE	QA Contact:	John Matthews <jmatthew>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	530	CC:	dparker, ssalevan
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	sat530	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-10 19:54:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	456996

Description Justin Sherrill 2008-11-06 19:26:22 UTC

In the two api calls user.setDefaultSystemGroup(s) if you pass in a system group to be the default and include a group that the target user is not an admin of, you get an error saying "Unable to locate or access server group".  

As soon as you set that user to be the admin of the group then the error goes away.

This behaviour is different from the WebUI which allows you to select groups to be the default for a user regardless of if that user is an admin of the group or not.


This is tested in the api automated unit tests.

Comment 1 Justin Sherrill 2008-11-06 20:00:32 UTC

Also the case with removeDefaultSystemGroup(s)

Comment 2 Justin Sherrill 2008-11-06 20:16:54 UTC

fixed in  b3f2cb7..2f70890

Comment 3 John Matthews 2009-01-23 20:42:48 UTC

Looking at commit:
http://git.fedorahosted.org/git/?p=spacewalk.git;a=commit;h=2f70890dca848899a6b5055a22df67a71082d72a

I'm assuming the API calls are 
user.addDefaultSystemGroup(s)  and not "setDefaultSystemGroup(s)".



Verified against: Satellite-5.3.0-RHEL5-re20081223.1-i386-embedded-oracle.iso

Comment 4 Brad Buckingham 2009-02-17 16:58:54 UTC

*** Bug 465094 has been marked as a duplicate of this bug. ***

Comment 5 Brandon Perkins 2009-09-10 19:54:01 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1434.html