Bug 1622994 – [downstream clone - 4.2.6] IO-Threads is enabled inadvertently by editing unrelated configuration

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	4.2.5
Hardware:	x86_64 Linux

Priority	high Severity urgent
Target Milestone:	ovirt-4.2.6
Target Release:	---
Assigned To:	Arik
QA Contact:	Liran Rotenberg
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	1619866
Blocks:
	Show dependency tree / graph

Reported:	2018-08-28 07:16 EDT by RHV Bugzilla Automation and Verification Bot
Modified:	2018-10-04 08:36 EDT (History)
CC List:	12 users (show)

See Also:
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.
Story Points:	---
Clone Of:	1619866
Environment:
Last Closed:	2018-09-04 09:41:42 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	3572221	None	None	None	2018-08-28 07:17 EDT
oVirt gerrit	93854	master	MERGED	core: always write num of i/o threads to ovf	2018-08-28 07:17 EDT
oVirt gerrit	93858	ovirt-engine-4.2	MERGED	core: always write num of i/o threads to ovf	2018-08-28 07:17 EDT
Red Hat Product Errata	RHBA-2018:2623	None	None	None	2018-09-04 09:42 EDT

Groups: None (edit)

Description RHV Bugzilla Automation and Verification Bot 2018-08-28 07:16:48 EDT

+++ 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):
ovirt-engine-4.2.5.3-1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
As above

Actual results:
IO Threads Enabled

Expected results:
IO Threads Disabled

(Originally by Germano Veit Michel)

Comment 6 RHV Bugzilla Automation and Verification Bot 2018-08-28 07:17:21 EDT

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 Bugzilla Automation and Verification Bot 2018-08-28 07:17:26 EDT

Verified on:
ovirt-engine-4.2.6.4-0.0.master.20180823141941.gitb3a5b18.el7.noarch

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.

Results:
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 09:33:41 EDT

Verified on:
ovirt-engine-4.2.6.4-0.1.el7ev.noarch

Same steps as in comment #7

Comment 12 errata-xmlrpc 2018-09-04 09:41:42 EDT

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/RHBA-2018:2623

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