Bug 1622994 - [downstream clone - 4.2.6] IO-Threads is enabled inadvertently by editing unrelated configuration
Summary: [downstream clone - 4.2.6] IO-Threads is enabled inadvertently by editing unr...
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.2.5
Hardware: x86_64
OS: Linux
Target Milestone: ovirt-4.2.6
: ---
Assignee: Arik
QA Contact: Liran Rotenberg
Depends On: 1619866
TreeView+ depends on / blocked
Reported: 2018-08-28 11:16 UTC by RHV bug bot
Modified: 2021-12-10 17:19 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, when the IO threads setting was disabled, if some other properties of a running virtual machine were changed, and then virtual machine was then shut down, the IO threads setting would be enabled. In this release, the IO threads setting is now properly saved into a next-run configuration. When the virtual machine is restarted, the IO threads setting remains disabled.
Clone Of: 1619866
Last Closed: 2018-09-04 13:41:42 UTC
oVirt Team: Virt
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44260 0 None None None 2021-12-10 17:19:05 UTC
Red Hat Knowledge Base (Solution) 3572221 0 None None None 2018-08-28 11:17:41 UTC
Red Hat Product Errata RHBA-2018:2623 0 None None None 2018-09-04 13:42:30 UTC
oVirt gerrit 93854 0 master MERGED core: always write num of i/o threads to ovf 2020-03-01 16:20:17 UTC
oVirt gerrit 93858 0 ovirt-engine-4.2 MERGED core: always write num of i/o threads to ovf 2020-03-01 16:20:17 UTC

Description RHV bug bot 2018-08-28 11:16:48 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1619866 +++

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

(Originally by Germano Veit Michel)

Comment 6 RHV bug bot 2018-08-28 11:17:21 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

(Originally by michal.skrivanek)

Comment 7 RHV bug bot 2018-08-28 11:17:26 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.

(Originally by Liran Rotenberg)

Comment 10 Liran Rotenberg 2018-08-29 13:33:41 UTC
Verified on:

Same steps as in comment #7

Comment 12 errata-xmlrpc 2018-09-04 13:41:42 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.


Note You need to log in before you can comment on or make changes to this bug.