Red Hat Bugzilla – Bug 1623447
[downstream clone - 4.2.6] Pending change IO thread disable is not applied on shutdown
Last modified: 2018-09-04 09:42:33 EDT
+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1619474 +++ ====================================================================== Description of problem: The VM is up and the user disables IO Threads and accepts this will be applied on next restart. But on next restart the old setting is still there. Version-Release number of selected component (if applicable): ovirt-engine-4.2.5.3-1.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Power up the VM with IO threads enabled 2. Disable IO Threads, confirm Setting will be applied later (OK) 3. Shutdown the VM 4. Start the VM Note: at item 2, if you click on edit again, the IO Thread setting is checked. Actual results: ovirt-engine-4.2.5.3-1.el7.noarch Expected results: IO Threads Disabled Additional information: The other way around (enabling IO threads) seem to work. It seems to only update Rng(?) and Graphics(?) on shutdown. 2018-08-21 10:40:09,668+10 INFO [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-1632) [6e6432c9] Running command: ProcessDownVmCommand internal: true. 2018-08-21 10:40:09,893+10 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (EE-ManagedThreadFactory-engine-Thread-1632) [53f4758c] Running command: UpdateVmCommand internal: true. Entities affected : ID: 42100647-bc71-4633-bad9-8723449a8e24 Type: VMAction group EDIT_VM_PROPERTIES with role type USER 2018-08-21 10:40:09,927+10 INFO [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (EE-ManagedThreadFactory-engine-Thread-1632) [2bbb4346] Running command: UpdateRngDeviceCommand internal: true. Entities affected : ID: 42100647-bc71-4633-bad9-8723449a8e24 Type: VMAction group EDIT_VM_PROPERTIES with role type USER 2018-08-21 10:40:09,947+10 INFO [org.ovirt.engine.core.bll.UpdateGraphicsDeviceCommand] (EE-ManagedThreadFactory-engine-Thread-1632) [1ce39d29] Running command: UpdateGraphicsDeviceCommand internal: true. Entities affected : ID: 42100647-bc71-4633-bad9-8723449a8e24 Type: VMAction group EDIT_VM_PROPERTIES with role type USER 2018-08-21 10:40:09,976+10 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1632) [1ce39d29] EVENT_ID: SYSTEM_UPDATE_VM(253), VM CentOS configuration was updated by system. (Originally by Germano Veit Michel)
Sharon? (Originally by michal.skrivanek)
(In reply to Michal Skrivanek from comment #1) > Sharon? This is a regression in 4.2.5 due to patch [1] which enabled IO threads as default for Server VM type. The reason is that in case IO threads is disabled, it is not written/read by OvfReader.java and vmBase default value is used. Up till 4.2.5 the default value was 0 and in mentioned patch [1] it was changed to 1. [1] https://gerrit.ovirt.org/#/c/92776/ (Originally by Sharon Gratch)
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 enabled. 2. Start the VM. 3. Disable IO-Threads (confirm that the change require VM restart). 4. Restart the VM. 5. Check the VM IO-Threads. Results: The VM IO-Threads was changed and disabled. (Originally by Liran Rotenberg)
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops@redhat.comINFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops@redhat.com (Originally by rhv-bugzilla-bot)
This patch already merged on the last 4.2.6 d/s build. Verified on: ovirt-engine-4.2.6.4-0.1.el7ev.noarch Same steps as in comment #5
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