+++ This bug was initially created as a clone of Bug #1035719 +++ Description of problem: Add an (engine-wide) option to configure default VNC client console mode (both SPICE and RDP have this option already). Reason: Since there are multiple invocation methods for VNC available, it makes sense to have the default invocation method configurable (as in SPICE and RDP case). --- Additional comment from Frantisek Kobzik on 2013-11-28 09:02:53 EST --- Merged U/S as 5371c0815633adc9de37d10e657c31795b38475e --- Additional comment from Frantisek Kobzik on 2013-12-02 07:58:11 EST --- --- Additional comment from Sandro Bonazzola on 2014-01-13 08:56:29 EST --- oVirt 3.4.0 alpha has been released including the fix for this issue. --- Additional comment from Yedidyah Bar David on 2014-01-23 05:15:53 EST --- 1. Installed ovirt-engine from 3.4 beta and setup 2. Verified that if creating a VM with display protocol VNC, it defaults to Native client 3. Did 'engine-config -s ClientModeVncDefault=NoVnc' and then 'service ovirt-engine restart' 4. Created a VM with display VNC, started it, opened console, NoVNC was started
Please review this TCMS test case: https://tcms.engineering.redhat.com/case/337017/?from_plan=3736 Thanks, Ilanit
Hi Ilanit, i've just sent you an email.
Verified on ovirt-3.4.0-beta3 Run TCMS test plan, and it passed: https://tcms.engineering.redhat.com/run/118597/
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html