Bug 1624015

Summary:	[RFE] Expose Console Options and Console invocation via API
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Andrea Perotti <aperotti>
Component:	ovirt-engine	Assignee:	Sharon Gratch <sgratch>
Status:	CLOSED ERRATA	QA Contact:	Ivana Saranova <isaranov>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.5	CC:	abpatil, ahadas, lsurette, michal.skrivanek, sgratch, sirao, srevivo
Target Milestone:	ovirt-4.5.0	Keywords:	FutureFeature, Reopened, ZStream
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.0	Doc Type:	Enhancement
Doc Text:	Feature: Setting the default console type (for both new and existing VMs) can be done engine widely by using CLI for setting the following engine-config parameters: `engine-config -s ClientModeVncDefault=NoVnc` to prefer NoVnc instead of remote-viewer and `engine-config -s ClientModeConsoleDefault=vnc` to prefer VNC over SPICE in case the VM has both available. If the actual console type for existed VMs was chosen manually via 'console options' dialog, cleaning the browser local storage is needed. So in case it's required to set console type globally for all existing VMs, please clear the browser local storage after running the engine. Reason: An option for setting default console type for all provisioned VMs globally at once was not supported up till now. Needed to go one VM by one and set the console type via the 'console options' dialog. Result: Support setting console type globally for all VMs, existed and new ones, by using the engine-config parameters.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-26 16:22:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	UX	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1171924
Bug Blocks:	1417161, 1541529

Description Andrea Perotti 2018-08-30 16:41:50 UTC

Description of problem:

Currently it's not possible to do via API or CLI:
- select the console type (Spice vs VNC) in case of VMs with both graphics stacks
- select console invocations options (VNC Native or NoVNC? Maps ctrl-alt-del to ctrl-alt-end?) 

At the moment is only possible to set the default value for newly created VMs via:

# engine-config -s ClientModeVncDefault=NoVnc
# systemctl restart ovirt-engine

but once the VM is provisioned, there's no way to change it.

This is a huge stopper for massive deployment

Version-Release number of selected component (if applicable):
RHV 4.2.


An initial improvement would be a command that enforce the default mode on also already provisioned VMs, if directly exposing an API for changing those values could take longer.

Comment 1 Siddhant Rao 2018-11-06 15:19:06 UTC

Hello,

Are there any updates on this Bug?.

Comment 5 Ryan Barry 2019-01-21 14:54:27 UTC

Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both

Comment 8 Michal Skrivanek 2019-09-06 06:57:10 UTC

unlike many other bugs where the "Depends On" is a loose dependency, this one really does depend on that RFE bug 1171924

Comment 14 Michal Skrivanek 2022-01-27 15:06:41 UTC

default behavior can be set engine-wide using CLI:
engine-config -s ClientModeVncDefault=NoVnc to prefer novnc instead of remote-viewer
and ClientModeConsoleDefault=vnc to prefer vnc over spice in case the VM has both available.

Comment 19 Ivana Saranova 2022-04-20 14:08:16 UTC

Steps:
1) Change default console for webadmin:

``` engine-config -s ClientModeConsoleDefault=spice ```

or

``` engine-config -s ClientModeConsoleDefault=vnc ```

2) Check that console is the one from the command if both VNC and Spice consoles are allowed on the VM.
3) Check that console is not the one from the command if it isn't allowed on the VM
4) Check that default console is not changed in VM Portal

Results:
VM portal default console setting is the same as it was before the command. The default console is successfully changed to the one from the command unless that type isn't allowed, then it's the type that is allowed.

Verified in:
ovirt-engine-4.5.0.2-0.7.el8ev.noarch

Comment 24 errata-xmlrpc 2022-05-26 16:22:26 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: RHV Manager (ovirt-engine) [ovirt-4.5.0] security 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-2022:4711