Description of problem: When logging in to user portal using a user with only "UserRole" permission assigned to it, the option to click on "new VM" is available. Opening new VM dialogue shows incorrect error message: "Not available when no Data Center is up" Also, all the fields in this dialogue are grayed out. Screenshot attached. Version-Release number of selected component (if applicable): oVirt Engine Version: 3.6.0-0.0.master.20150519172219.git9a2e2b3.el6 How reproducible: constantly Steps to Reproduce: 1. Add active directory domain and restart ovirt-engine service. 2. Navigate to "Users" tab and add active directory user. 3. Navigate to configure > system permissions and add active directory user with role to asign: "UserRole" 4. open user poratal with active directory user. 5. Click on "New VM". Actual results: new VM dialogue opened and an incorrect error message appears: "Not available when no Data Center is up" Expected results: "new VM" dialogue should be unavailable (grayed out) when using user without permissions to create VM. Additional info: Screenshot attached.
Created attachment 1032863 [details] UI screenshot
is the request here to grey out the dialog, or the action-button? if the dialog: the dialog is already greyed out, as seen in the screen-shot. the message can be phrased better. something like: "Not available when no Data-Center is up or when there are insufficient permissions to perform the action". if the action-button: this BZ should depend on bug 1221694 - it doesn't make sense to apply the greying-out behaviour only to the New VM action - it should be applied across all of the UI (web-admin, user-portal) for all actions on all objects.
The error message was incorrect, there was a data center up as you can see in the screenshot one of the VMs is up. thus the bug i opened. Either way, depending this bug on bug 1221694 make sense, the "New VM" button should be grayed out when user role does not have these permissions.
moved off to 4.0 per scrub mtg
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
pushed out due to capacity reasons
This may be addressed in a new user portal but will not fit into 4.1 - pushing to 4.2.
tracking upstream: https://github.com/oVirt/ovirt-web-ui/issues/286