Bug 1371789 - Unable to open guest console from user portal with superuser role permission.
Summary: Unable to open guest console from user portal with superuser role permission.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.8
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-31 06:30 UTC by Ameya Charekar
Modified: 2021-08-30 12:17 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-07 09:00:48 UTC
oVirt Team: Virt
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43205 0 None None None 2021-08-30 12:09:38 UTC
Red Hat Knowledge Base (Solution) 2625971 0 None None None 2017-12-22 05:19:49 UTC

Description Ameya Charekar 2016-08-31 06:30:35 UTC
Description of problem:

Not able to open guest console from user portal with user having superuser role permission to a vm.

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

rhevm-3.6.8.1-0.1.el6.noarch

How reproducible:

Always.

Steps to Reproduce:
1. Add permission to user with SuperUser role for a vm.
2. Login with SuperUser from user portal.
3. Take console of vm.

Actual results:

Can't find VM with id <vm_id>.

Expected results:

Able to take console of vm.

Additional info:

We can take vm console after adding UserRole permission to same user.
Working as expected in rhev 3.5.

Comment 1 Tomas Jelinek 2016-08-31 07:55:55 UTC
The user portal does not use the admin roles, it uses user roles. Actually in user portal you should not even see the VM if you don't have UserRole on it.

How did you get to the state that you can see it? Can you do any operations on it? What exact roles the user you used has?


Note You need to log in before you can comment on or make changes to this bug.