Description of problem: UserVmManager/PowerUser can not reassign existing VM to a different cluster within the same DC. User has to pick the correct one right at VM creation. Version-Release number of selected component (if applicable): si19.1 / rhevm-backend-3.1.0-18.el6ev.noarch How reproducible: always Steps to Reproduce: 1. have a DC with two clusters and user with PowerUserRole on whole DC 2. as the user, create a VM in PUP 3. edit the (down, idle) VM, try to change Cluster Actual results: in step 2: you can choose both clusters - correct in step 3: only the current cluster is available in drop-down menu Expected results: step 2: the same step 3: user should be able to choose among both clusters Additional info: this works fine in 3.0, thus marking as a regression
In the Edit existing VM dialog, the UI shows only clusters on which you have EDIT_VM_PROPERTIES action group on. We changed the PowerUser role to a creator role, thus he no longer has this permission. It seems reasonable to me to show all clusters with a CREATE_VM permission on the cluster, as by updating a VM cluster you basically create a new VM in this cluster. Miki - any thoughts on that?
Patch posted to gerrit: http://gerrit.ovirt.org/#/c/8724/
Commit: 5627c6402f9b0ab71728f364705a29dce48e6f72 http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=5627c6402f9b0ab71728f364705a29dce48e6f72
3.2 has been released