Description of problem: We use oVirt for VDI and have VM pools where the display options of the VM have both spice and VNC options. In the past, users who use the web-ui could select the console type based on their client (Linux/Windows using remote-viewer can select spice, Mac has to use the noVNC option in the browser). Since the upgrade of ovirt-web-ui to 1.6.8 this is no longer possible. There's only a single "Console" option and it always defaults to "vnc". Users no longer have the option to specify a different console type. In our case, spice is no longer used, which means usb passhthrough fails etc. From the rpm changelog I see "enhance graphic consoles data fetching time by fetching consoles info on demand instead of on refresh. This changes the way consoles are opened on dashboard". This change may be relevant? Is there any way to allow the user to select the console type with the new web-ui version? Version-Release number of selected component (if applicable): ovirt-web-ui-1.6.8-1.el8.noarch How reproducible: Steps to Reproduce: 1. Create a VM that has both VNC and SPICE console options 2. Log in on web-ui and start the VM 3. Try to select a SPICE console Actual results: No option to select console type and defaults to VNC Expected results: Option to select console type as before so SPICE console can be selected. Additional info:
(In reply to Rik Theys from comment #0) > Description of problem: > We use oVirt for VDI and have VM pools where the display options of the VM > have both spice and VNC options. > > In the past, users who use the web-ui could select the console type based on > their client (Linux/Windows using remote-viewer can select spice, Mac has to > use the noVNC option in the browser). > > Since the upgrade of ovirt-web-ui to 1.6.8 this is no longer possible. > There's only a single "Console" option and it always defaults to "vnc". > Users no longer have the option to specify a different console type. In our > case, spice is no longer used, which means usb passhthrough fails etc. > > From the rpm changelog I see "enhance graphic consoles data fetching time by > fetching consoles info on demand instead of on refresh. This changes the way > consoles are opened on dashboard". This change may be relevant? This is indeed the relevant change. It was done for solving performance issues on web-ui. Anyway, it is only a 1st phase solution since we are planning to support console options settings per user such that the user will be enable to configure which console type to use by default via the VM portal itself. > > Is there any way to allow the user to select the console type with the new > web-ui version? Sure, the current way to change the console default type is by the setting the following engine config values: ClientModeConsoleDefault, ClientModeVncDefault ClientModeConsoleDefault - Default console type to use, options: vnc,spice. Default is vnc. ClientModeVncDefault - Default VNC console invocation type. options: Native,NoVnc. Default is Native. **If ClientModeConsoleDefault is set to VnC then ClientModeVncDefault will determine the VNC invocation type. For checking current values, just use the engine configuration tool by running: $ENGINE-HOME/bin/engine-config -g ClientModeConsoleDefault $ENGINE-HOME/bin/engine-config -g ClientModeVncDefault For changing the default to SPICE for example, run: $ENGINE-HOME/bin/engine-config -s ClientModeConsoleDefault=spice and then restart the ovirt-engine service to load changes: systemctl restart ovirt-engine.service > > > Version-Release number of selected component (if applicable): > ovirt-web-ui-1.6.8-1.el8.noarch > > How reproducible: > > > Steps to Reproduce: > 1. Create a VM that has both VNC and SPICE console options > 2. Log in on web-ui and start the VM > 3. Try to select a SPICE console > > Actual results: > No option to select console type and defaults to VNC > > Expected results: > Option to select console type as before so SPICE console can be selected. > > Additional info: It's not a bug since it's intentionally implemented like this (check https://bugzilla.redhat.com/show_bug.cgi?id=1795457) and planned to be more user friendly once user settings for consoles is supported.
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
(In reply to Sharon Gratch from comment #1) > (In reply to Rik Theys from comment #0) > > Is there any way to allow the user to select the console type with the new > > web-ui version? > > > Sure, the current way to change the console default type is by the setting > the following engine config values: ClientModeConsoleDefault, > ClientModeVncDefault > ClientModeConsoleDefault - Default console type to use, options: vnc,spice. > Default is vnc. > ClientModeVncDefault - Default VNC console invocation type. options: > Native,NoVnc. Default is Native. > > **If ClientModeConsoleDefault is set to VnC then ClientModeVncDefault will > determine the VNC invocation type. > > > For checking current values, just use the engine configuration tool by > running: > $ENGINE-HOME/bin/engine-config -g ClientModeConsoleDefault > $ENGINE-HOME/bin/engine-config -g ClientModeVncDefault > > > For changing the default to SPICE for example, run: > $ENGINE-HOME/bin/engine-config -s ClientModeConsoleDefault=spice > > and then restart the ovirt-engine service to load changes: > systemctl restart ovirt-engine.service > I forgot to mention that the option of selecting the console type from within the VM details view on web-ui is still supported as it was before 1.6.8 version: Click on the VM card from the VMs dashboard view -> on the upper left side click on the "Console" menu for selecting the supported console to open.
For supporting the option to set the default global graphic console type for all VMs via web-ui, check https://github.com/oVirt/ovirt-web-ui/issues/1398 Please note that it will be set for all VMs and not per VM as existed on webadmin's console options.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Based on comment 1 and comment 3 it's not really a regression so removing the regression flag
This should be postponed to 4.4.7 since it's too late for changing apis for https://gerrit.ovirt.org/114302
With performance improvements added [1] it should be possible to bring back the previous functionality. [1] https://gerrit.ovirt.org/c/ovirt-engine/+/114302
Steps: 1) Login to VM Portal 2) Check that VM with Spice+VNC console support has all the console options in the menu on main page and in the VM details 3) Check that default console type can be set in the global settings Results: Default console type can be set in the global settings and unless the VM has that default option disabled (for example default VNC, but only Spice supported on the VM), the default option is shown as the first option in the VM menu on the VM Portal main page if it's running. All of the consoles are listed if user clicks on the droplist menu of the VM and all of them redirect to the correct type. In VM details the console types are listed in the console menu button, again all of them and all of them are working correctly. If the VM is down, there is no console option on the main page and the console button in the VM details is disabled. Verified in: ovirt-web-ui-1.7.0-1.el8ev.noarch ovirt-engine-4.4.7.5-0.9.el8ev.noarch
This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.7 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.