Bug 1309289

Summary:	Inconsistent behaviour between disk profiles and CPU profiles
Product:	[oVirt] ovirt-engine	Reporter:	Tomer Saban <tsaban>
Component:	General	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	future	CC:	bugs, dfediuck, iheim, mgoldboi, rgolan, tsaban
Target Milestone:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-21 09:19:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Tomer Saban 2016-02-17 11:51:06 UTC

Description of problem:
When adding CPU Profile the default permissions that are added are different than when adding Disk Profile. 

Additional info:
CPU Profile related roles: CpuProfileOperator, CpuProfileCreator
Disk Profile related roles: DiskProfileCreator, DiskProfileOperator, DiskProfileUser.

Should be consistent as well with each other.

Comment 1 Roy Golan 2016-02-21 09:19:55 UTC


*** This bug has been marked as a duplicate of bug 1309287 ***