Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1344267

Summary:	The parameter "IO Threads" set in running vm not updated after vm restart.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ameya Charekar <achareka>
Component:	ovirt-engine	Assignee:	Sharon Gratch <sgratch>
Status:	CLOSED ERRATA	QA Contact:	Shira Maximov <mshira>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.6.6	CC:	bloch, gklein, lsurette, mgoldboi, michal.skrivanek, mshira, rbalakri, Rhev-m-bugs, sgratch, srevivo, ykaul
Target Milestone:	ovirt-4.0.0-rc3
Target Release:	4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 20:41:34 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:
Embargoed:

Description Ameya Charekar 2016-06-09 09:52:11 UTC

Description of problem:

After enabling "IO Threads" below message appears:
~~~
Changes that require Virtual Machine restart:
numOfIoThreads
~~~
But once vm is down option "IO Threads" is disabled again.

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

Red Hat Enterprise Virtualization Manager Version: 3.6.6.2-0.1.el6

How reproducible:
Always

Steps to Reproduce:
1. Enable "IO Threads" of running vm.
2. Shutdown vm
3. Check "IO Threads" parameter.

Actual results:

Unable to change "IO Threads" on running vm.

Expected results:

Enabling "IO Threads" on running vm should persist.

Additional info:

Currently we need to shutdown vm before changing "IO Threads". But disabling "IO Threads" on running vm works as expected.

Comment 2 Sharon Gratch 2016-06-27 12:33:01 UTC

I reproduced the bug on 3.6.6. The bug was that changing the IO Threads configuration (by enabling "IO Threads" and/or changing "num of io threads") is just not saved after exiting the dialog. i.e. after enabling the "IO Threads"  and pressing the ok button, its not saved and return back to be disabled. If you will open the dialog again, the "IO Threads" is back to be disabled even before you shutdown the vm.

The snapshot with the changed configuration is saved for the vm in db, but since the configuration is marked as disabled, the "IO Threads" configuration is not changed after vm restart.


Anyway, it was fixed for 4.0 and therefore I close this bug.

Comment 5 Shira Maximov 2016-07-04 14:11:00 UTC

verified on :
Red Hat Enterprise Virtualization Manager Version: 4.0.2-0.2.rc1.el7ev

verification steps : 
1. Enable "IO Threads" of running vm.
2. Shutdown vm
3. Check "IO Threads" parameter.

Comment 6 Yaniv Kaul 2016-07-05 05:09:02 UTC

(In reply to Shira Maximov from comment #5)
> verified on :
> Red Hat Enterprise Virtualization Manager Version: 4.0.2-0.2.rc1.el7ev
> 
> verification steps : 
> 1. Enable "IO Threads" of running vm.
> 2. Shutdown vm
> 3. Check "IO Threads" parameter.

And is it really working when the VM is running?

Comment 7 Shira Maximov 2016-07-24 12:31:24 UTC

(In reply to Yaniv Kaul from comment #6)
> (In reply to Shira Maximov from comment #5)
> > verified on :
> > Red Hat Enterprise Virtualization Manager Version: 4.0.2-0.2.rc1.el7ev
> > 
> > verification steps : 
> > 1. Enable "IO Threads" of running vm.
> > 2. Shutdown vm
> > 3. Check "IO Threads" parameter.
> 
> And is it really working when the VM is running?

it's working only after shotdown

Comment 9 errata-xmlrpc 2016-08-23 20:41:34 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.

https://rhn.redhat.com/errata/RHEA-2016-1743.html