Bug 1619866

Summary: IO-Threads is enabled inadvertently by editing unrelated configuration
Product: Red Hat Enterprise Virtualization Manager Reporter: Germano Veit Michel <gveitmic>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED ERRATA QA Contact: Liran Rotenberg <lrotenbe>
Severity: urgent Docs Contact:
Priority: high    
Version: 4.2.5CC: ahadas, bcholler, gveitmic, lsurette, mavital, michal.skrivanek, mtessun, Rhev-m-bugs, sborella, srevivo, tburke
Target Milestone: ovirt-4.3.0Keywords: ZStream
Target Release: 4.3.0Flags: ahadas: needinfo-
Hardware: x86_64   
OS: Linux   
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: Bug Fix
Doc Text:
This release ensures that if a request occurs to disable I/O threads of a running VM, the I/O threads setting remains disabled when changing unrelated properties of a running VM.
Story Points: ---
Clone Of:
: 1622994 (view as bug list) Environment:
Last Closed: 2019-05-08 12:38:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1622994    

Description Germano Veit Michel 2018-08-22 00:31:33 UTC
Description of problem:

We have a report of a customer that does not wish to use IO-Threads and after upgrade to 4.2.5 all VMs are getting randomly IO-Threads enabled.

To reproduce:
1. Create VM with IO Threads Disabled
2. Power up the VM
3. Edit the VM, i.e. disable Memory Baloon*
4. Click OK
RESULT: IO Threads is enabled for the next-run

* Any config that triggers next-run config seems to do it. Only seem to happen if the VM is up.

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

How reproducible:

Steps to Reproduce:
As above

Actual results:
IO Threads Enabled

Expected results:
IO Threads Disabled

Comment 4 Michal Skrivanek 2018-08-22 06:36:20 UTC
it should be the same root cause (and same fix eventually) as bug 1619474
But I would prefer to keep this bug opened to independently verify both flows

Comment 5 Liran Rotenberg 2018-08-26 12:16:15 UTC
Verified on:

Steps of verification:
1. Create a new VM with IO-Threads disabled.
2. Start the VM.
3. Change a VM property - for example disabled ballooning (confirm that the change require VM restart).
4. Check the VM configuration for next-run (IO-Threads should be disabled).
4. Restart the VM.
5. Check the VM IO-Threads.

The VM IO-Threads was disabled all along and didn't change when editing other VM property.

Comment 9 errata-xmlrpc 2019-05-08 12:38:08 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, and where to find the updated
files, follow the link below.

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