| Summary: | HE-VM's serial console is shown in shell, although it was not enabled via WEBUI | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Nikolai Sednev <nsednev> | ||||
| Component: | VMConsole | Assignee: | Francesco Romani <fromani> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | meital avital <mavital> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.0.4 | CC: | bugs, michal.skrivanek, nsednev | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| Target Release: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-09-07 10:14:47 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: | |||||
| Attachments: |
|
||||||
|
Description
Nikolai Sednev
2016-09-05 06:11:09 UTC
Created attachment 1197756 [details]
HE-VM serial console was not enabled and not marked via WEBUI, but appears via the shell.
I suppose the existence of serial console is intentional for HE. Not sure about permissions (In reply to Michal Skrivanek from comment #2) > I suppose the existence of serial console is intentional for HE. Not sure > about permissions I have not set permissions for HE-VM to get serial console allowed as I did for other 2 VMs, even though, HE-VM appears in shell. HE-VM's default permissions that I see are: SuperUser UserProfileEditor Guest-VM's exposed to serial console have permissions of: UserVmManager SuperUser UserProfileEditor The UserVmManager permission is a must for getting the VM shown in serial console's shell. SuperUser as well (on the VM entity). Is that who you were connecting with? (In reply to Michal Skrivanek from comment #4) > SuperUser as well (on the VM entity). Is that who you were connecting with? I think so. I see that only with SuperUser I'm getting the serial-console. Should've it been changed for UserVmManager, as the one and only permission for serial console? (In reply to Nikolai Sednev from comment #5) > (In reply to Michal Skrivanek from comment #4) > > SuperUser as well (on the VM entity). Is that who you were connecting with? > > I think so. I see that only with SuperUser I'm getting the serial-console. Then it works correctly. > Should've it been changed for UserVmManager, as the one and only permission > for serial console? Why? See bug 1320343 Is there still anything to look at from original description or we're all good now? Sounds like my bug is actually not a bug at all, as not only UserVmManager permission is required, but UserInstanceManager or SuperUser are sufficient. Please consider closing this one as not a bug. ok. thanks |