Description of problem:
VirtIO serial console is not working with superuser role (tried with admin@internal).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enable VirtIO serial console.
2. Copy public key of the client machine.
3. ssh -t -p 2222 ovirt-vmconsole@MANAGER_IP.
ERROR: No available running VMs
Connection to MANAGER_IP closed.
We should get serial console with SuperUser role. As per documentation, to access the serial console of a virtual machine, the user must have the UserVmManager, SuperUser, or UserInstanceManager permission on that virtual machine.
Adding role UserVmManager resolves the issue.
We suspect an underlying role/permission management issue.
Could be related to https://bugzilla.redhat.com/show_bug.cgi?id=1313904
We will continue the investigation to pinpoint the root cause.
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.
Best would be to solve the "VM visibility problem" in console servlet, just so it behaves the same as the rest of the system
works for admin@internal and an AD user with both UserVmManager and UserInstanceManager roles (it needs UserProfileEditor role so the user could modify his profile, ie. to upload this public ssh key).
DocText is odd, there appears twice 'UserInstanceManager'.
right, the doc text was wrong - fixed.
But the verification was not correct, both UserVmManager and UserInstanceManager roles worked also before. The issue was that also the SuperUser did not work, so also this role needs to be checked.
SuperUser works fine - admin@internal - but tested also with an AD user with this role too ;)