Description of problem: usb forwarding does not work on VMs/templates created in 3.6 after upgrading to 4.2.7 Version-Release number of selected component (if applicable): RHV 4.2.7 How reproducible: always at customer site Steps to Reproduce: 1. have vm/pool/template created in RHEV 3.6 with usb redirection enabled 2. upgrade to 4.2.7 and change compatibility level to 4.2 Actual results: after vm/pool/template will gain 4.2 compatibility level usb redirection will stop working Expected results: after vm/pool/template will gain 4.2 compatibility level usb redirection will be working Additional info: when you disable usb redirectio and enable again it start working again
To clarify, is this VMs, pools, templates, or all? The test case you provided works, but trying to ensure all scenarios are covered
It was reported that all of them are affected, i.e. VMs, Pools and templates.
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ] For more info please contact: rhv-devops
Verified on: ovirt-engine-4.3.1.1-0.1.el7.noarch Steps: 1. Deploy RHV 4.1. 2. Create VM, VM from a template, and a pool. 3. Set console to SPICE and enabled usb redirection. 4. Run the VMs ( Also have some down VMs). 5. Upgrade to 4.2 and change compatibility level to 4.2. 6. Upgrade to 4.3 and change compatibility level to 4.3. 7. Reboot the running VMs, Start the down VMs. 8. Check the USB redirection running in the engine: # /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select type, device, address, is_managed, is_plugged, alias from vm_device_view where vm_id in (select vm_guid from vm_static where vm_name='<VM_NAME>') and device='spicevmc';" In the result check for USB devices, type=redir, set with address, is_managed and is_plugged set to true and the device has alias. Results: The above VMs that were made in 4.1 with USB redirection, after moving to 4.3 without a reboot: type | device | address | is_managed | is_plugged | alias ---------+----------+---------------------------------------------------+------------+------------+---------- redir | spicevmc | {type=usb, bus=0, port=4} | t | t | redir3 redir | spicevmc | {type=usb, bus=0, port=3} | t | t | redir2 redir | spicevmc | {type=usb, bus=0, port=1} | t | t | redir0 redir | spicevmc | {type=usb, bus=0, port=2} | t | t | redir1 channel | spicevmc | {type=virtio-serial, bus=0, controller=0, port=3} | f | t | channel2 (5 rows) After the reboot: type | device | address | is_managed | is_plugged | alias ---------+----------+---------------------------------------------------+------------+------------+----------------------------------------- redir | spicevmc | {type=usb, bus=0, port=4} | t | t | ua-adf66511-2c1f-47c0-9e77-565772892abc redir | spicevmc | {type=usb, bus=0, port=3} | t | t | ua-444ee508-e0fb-4839-9047-220bbc2bebcb redir | spicevmc | {type=usb, bus=0, port=1} | t | t | ua-00505a62-7f17-4166-be78-b1c394985550 redir | spicevmc | {type=usb, bus=0, port=2} | t | t | ua-1f85b62f-774e-4ba2-8e40-2954c8635fc4 channel | spicevmc | {type=virtio-serial, bus=0, controller=0, port=3} | f | t | channel2 (5 rows) Note: The fix is in 4.3, if the VM is rebooted in 4.2, a manual workaround will be needed: Disable USB redirection and enable it again
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Open patch attached] For more info please contact: rhv-devops
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. https://access.redhat.com/errata/RHEA-2019:1085
This looks to still be an issue with pooled VMs. Given this is the same issue with slightly different parameters should we clone this bug and continue working on it in a new bug? Thanks!
On 4.3? Have any details?