Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1480894

Summary: Inconsistent error messages when a VM console is in use
Product: Red Hat Enterprise Virtualization Manager Reporter: Allie DeVolder <adevolder>
Component: ovirt-web-uiAssignee: Marek Libra <mlibra>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.2CC: adevolder, bazulay, fromani, gshereme, mavital, michal.skrivanek, oourfali, Rhev-m-bugs, tjelinek
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-29 08:11:53 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 Allie DeVolder 2017-08-12 17:44:11 UTC 
Description of problem:
The error messages when failing to connect to a console that is in use by another user are not clear. It displays either "Failed to retrieve VM console details" or "Forbidden", depending on where you open the console from.

Version-Release number of selected component (if applicable):
4.1

How reproducible:
100%

Steps to Reproduce:
1. Create VM
2. Log in to new VM
3. As another user, attempt to log in to new VM while it's in use from the portal

Actual results:
Unclear error message

Expected results:
Notification that a user is currently logged in rather than a vague failure to connect
Comment 1 Michal Skrivanek 2017-08-13 07:01:33 UTC 
which portal?
Comment 2 Tomas Jelinek 2017-08-29 08:11:53 UTC 
It has been fixed upstream by https://github.com/oVirt/ovirt-web-ui/pull/204

The https://bugzilla.redhat.com/show_bug.cgi?id=1481212 rebased on this change and the 1.2.1 will contain this fix. Closing as duplicate of it.

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