Red Hat Bugzilla – Bug 888689
[User Portal] An user with UserRole assigned to a pool does not see pool's VMs
Last modified: 2013-06-10 17:29:33 EDT
Description of problem:
An user with UserRole assigned to a pool does not see pool's VMs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. New pool in Admin Portal (AP)
2. In AP -> Pools -> select pool -> Permissions -> Add --> an user with UserRole
3. Log in as previously defined user into User Portal
An user with UserRole for a pool cannot see/work with pool's VMs.
An user with UserRole for a pool can see/work with pool's VMs.
"UserRole - Can access and use virtual machines and pools. - Can log in to the User Portal, use assigned virtual machines and pools, view virtual machine state and details."
FYI, there was similar issue in the past - BZ839490.
Are you able to see/run the pool itself? From the description above it wasn't clear whether you can't see the pool, or the VMs.
Pools in user portal are shown, but the VMs aren't. Once you run the pool, one VM is assigned to you, and then you see it instead of the pool.
That's the behavior that you should see.
If you don't, then it is a bug.
No, nothing - neither pool nor VMs. Even if I login with 'admin@internal' into UP, i cannot see a pool.
*** Bug 896221 has been marked as a duplicate of this bug. ***
copy of the comment from the 896221 to have all relevant info on the active bug:
This bug is not connected with upgrade. It is an FE issue which will prevent you from see any VM or pool if you have a pool.
On U/S it has already been fixed some time ago:
Allan - is a test package relevant to test this fix for the customer you mentioned in bug 896221, comment 6?
this bug has been fixed upstream before rebase as 694d9f490bd554b64e41e34530bac5fa74a74a0f.
u/s gerrit: http://gerrit.ovirt.org/#/c/10172/
OK, sf4. For admin@internal issue - BZ904974, for seeing individual pooled VMs when UserRole on whole system - BZ904984.
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.