Bug 1826431

Summary:	Enable VNC Encryption cause noVNC Unsupported security types error
Product:	[oVirt] ovirt-engine	Reporter:	Tamir <tamir>
Component:	WebSocket Proxy	Assignee:	Liran Rotenberg <lrotenbe>
WebSocket Proxy sub component:	General	QA Contact:	Tamir <tamir>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	bugs, rbarry
Version:	4.4.0	Flags:	pm-rhel: ovirt-4.4+
Target Milestone:	ovirt-4.4.1
Target Release:	---
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:	2020-07-08 08:27:48 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:
Embargoed:

Description Tamir 2020-04-21 17:05:08 UTC

Description of problem:
When VNC Encryption is enabled in the cluster's console tab. Triggering NoVNC console results with: "Unsupported security types: 19".

Version-Release number of selected component (if applicable):
RHEV 4.4.0-31 (RHEL 8.2 engine + hosts)
RHEVM: org.ovirt.engine-root-4.4.0-33
VDSM: vdsm-4.30.44-1.el7ev
novnc-1.1.0-1.el8ost.noarch


How reproducible:
100%

Steps to Reproduce:
Note: Steps 1-2 are if the VNC encryption isn't set)
1. Set the cluster with VNC encryption(Cluster->Enable VNC Encryption)
2. Reinstall the host to apply the changes
3. Run VM with VNC console
4. Start NoVNC console to the VM.

Actual results:
Console isn't open, Got the error: "Unsupported security types: 19".

Expected results:
Console open as usual.

Additional info:
Liran previously opened a similar bug that was fixed. I attached it

Comment 1 Tamir 2020-05-24 10:49:06 UTC

Verified the fix in RHV 4.4.1-1 with RHEL 8.2 engine and hosts and it works!

Verification Steps:
1. Create a data center, cluster with VNC encryption, add a host and data domain.
2. Create a VM.
3. Run the VM with VNC console
4. Start NoVNC console to the VM.

Everything work as expected.

Comment 2 Sandro Bonazzola 2020-07-08 08:27:48 UTC

This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.