Bug 1386289

Summary: [z-stream clone - 3.6.10] User can't assign CPU profile after upgrade from 3.6 to 4.0
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Andrej Krejcir <akrejcir>
Status: CLOSED ERRATA QA Contact: Shira Maximov <mshira>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: akrejcir, dfediuck, fdelorey, gklein, jcoscia, jentrena, jspahr, lsurette, mgoldboi, michal.skrivanek, mkalinin, rbalakri, rgolan, rhev-integ, Rhev-m-bugs, rhodain, srevivo, ykaul
Target Milestone: ovirt-3.6.10Keywords: Regression, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: When checking permissions for a cpu profile group permissions were not considered. Consequence: Users part of a group could not assign a cpu profile and so could not start a vm. Fix: Use PermissionDao and correct SQL functions when checking permissions. Result: Group permissions are considered.
Story Points: ---
Clone Of: 1369046 Environment:
Last Closed: 2017-01-17 18:04:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1369046    
Bug Blocks:    

Comment 4 Michal Skrivanek 2016-11-01 12:34:41 UTC
*** Bug 1389764 has been marked as a duplicate of this bug. ***

Comment 5 Shira Maximov 2016-11-15 13:39:23 UTC
verified on : 
Red Hat Enterprise Virtualization Manager Version: 3.6.10-0.1.el6


verification steps:
1) Create a user X, a group  Y , and add the user  to the group
2) Remove the permissions CpuProfileOperator for 'Everyone' on a CPU profile
3) Add VmCreator permission for the user X on the cluster
4) Try to create a VM with the CPU profile in the userportal - WORK
5) Remove the permissions for the user 'X' and add the same permission for the group 'Y'
6) Create VM in the userportal - WORK

Comment 7 errata-xmlrpc 2017-01-17 18:04:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2017-0108.html