Bug 1278271
Summary: | User Portal reporting all DataCenter are down while creating a new VM from user portal | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Sarvesh Pandit <sapandit> |
Component: | ovirt-engine | Assignee: | jniederm |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.5.4 | CC: | gklein, jniederm, lsurette, mavital, rbalakri, Rhev-m-bugs, yeylon, ykaul |
Target Milestone: | ovirt-3.6.2 | ||
Target Release: | 3.6.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, a user couldn't create a virtual machine in the User Portal if they only had the InstanceCreator role permissions. It showed "Not available when no Data Center is up." in the New VM dialog even if there was a data center up. Now, the error message has been changed to a more meaningful "There is no Cluster on which you can create a VM. Please check Data Center status and Cluster permissions." Permission checking has been fixed so that InstanceCreator role permissions are sufficient to create a new virtual machine.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-09 21:14:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sarvesh Pandit
2015-11-05 06:52:32 UTC
please note that in the user portal, Clusters/DCs are displayed based on user's permissions (maybe also quota - not sure). so even if the problem reported here is not a bug, but simply a case of missing proper permissions, I would still recommend rephrase the message in the dialog specifically within the user portal to be something like: "Not available when no Data Center is up, or when permissions/quota is missing or misconfigured". Verified on 3.6.2-3 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-2016-0376.html |