Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2159768

Summary:	Regression in ClientModeVncDefault
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	schandle
Component:	ovirt-engine	Assignee:	Dana <delfassy>
Status:	CLOSED ERRATA	QA Contact:	Barbora Dolezalova <bdolezal>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5.3	CC:	emarcus, mperina, mzamazal
Target Milestone:	ovirt-4.5.3-async
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.3.6	Doc Type:	Bug Fix
Doc Text:	Code change for BZ2089299 introduced a regression, which didn't allow to set options in the engine-config which restricted the allowable values using the validValues field (for example ClientModeVncDefault or UserSessionTimeOutInterval). In this release, setting values for those fields works the same way as in RHV versions earlier than RHV 4.4 SP1 batch 3 (ovirt-engine-4.5.3).	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-14 13:09:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description schandle 2023-01-10 16:31:42 UTC

Description of problem:
When updating the default VNC console invocation behavior in the engine 'ClientModeVncDefault' not accepting the value of [Native,NoVnc]

Version-Release number of selected component (if applicable):
rhvm-4.5.3.4-1.el8ev.noarch

How reproducible:
100 %


Actual results:

# engine-config -g ClientModeVncDefault
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
ClientModeVncDefault: Native version: general

#  engine-config -s ClientModeVncDefault=NoVnc
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
Cannot set value NoVnc to key ClientModeVncDefault. Valid values are [Native,NoVnc]


Expected results:

# engine-config -g ClientModeVncDefault
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
ClientModeVncDefault: Native version: general

# engine-config -s ClientModeVncDefault=NoVnc
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false

# engine-config -g ClientModeVncDefault
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
ClientModeVncDefault: NoVnc version: general

Additional info:
The was working on 4.5.0, then when upgraded it no longer allows for the change.

Comment 1 Martin Perina 2023-01-11 10:28:26 UTC

This issue is most probably caused by a regression during implementation of BZ2089299

Comment 3 Barbora Dolezalova 2023-01-31 15:00:01 UTC

The 'ClientModeVncDefault' is accepting the values as expected:

# engine-config -g ClientModeVncDefault
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
ClientModeVncDefault: Native version: general

# engine-config -s ClientModeVncDefault=NoVnc
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false

# engine-config -g ClientModeVncDefault
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
ClientModeVncDefault: NoVnc version: general

Verified in ovirt-engine-4.5.3.7-0.zstream.20230125101610.gitf21a4b1784d.el8.noarch

Comment 5 errata-xmlrpc 2023-02-14 13:09:16 UTC

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 (Moderate: Red Hat Virtualization security and bug fix update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2023:0759