Bug 1988140

Summary:	VM console: Disconnect button to VNC console doesn't disconnect the console (doesn't close)
Product:	OpenShift Container Platform	Reporter:	Matthias Muench <mmuench>
Component:	Console Kubevirt Plugin	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED DUPLICATE	QA Contact:	Leon Kladnitsky <lkladnit>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.8	CC:	aos-bugs, cnv-qe-bugs, ycui
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-04 13:12:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthias Muench 2021-07-29 20:33:25 UTC

Description of problem:
When opening the Console for a VM, the Disconnect button for VNC console doesn't disconnect the console. 
However, according to [1], in the third paragraph, this is suggested:
"Console sessions remain active in the background unless they are disconnected. To ensure that only one console session is open at a time, click the Disconnect before switching check box before switching consoles."

[1] https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html-single/openshift_virtualization/index#virt-about-vm-console-sessions_virt-accessing-vm-consoles


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

How reproducible:
Always


Steps to Reproduce:
1. Start a VM 
2. go to the VM overview screen and select the Console
3. the Console is opened by default using VNC console and Disconnect button doesnt do anything

Actual results:
- VNC console: not disconnecting
- serial console: disconnecting

Expected results:
- in VNC and serial console mode it's disconnecting


Additional info:

Comment 1 Phillip Bailey 2021-08-04 13:12:53 UTC


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