Bug 1145665 - [engine-backend] [blkio-support] Hotplug disk doesn't include ioTune attribute
Summary: [engine-backend] [blkio-support] Hotplug disk doesn't include ioTune attribute
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: x86_64
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.5.0
Assignee: Martin Sivák
QA Contact: Elad
URL:
Whiteboard: sla
Depends On: 1166182
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-23 13:13 UTC by Elad
Modified: 2016-02-10 20:17 UTC (History)
12 users (show)

Fixed In Version: org.ovirt.engine-root-3.5.0-23
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:08:10 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Engine and vdsm logs (1.49 MB, application/x-gzip)
2014-09-23 13:13 UTC, Elad
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 33907 0 master MERGED core: Push ioTune QoS info when hotplugging disk Never
oVirt gerrit 35352 0 ovirt-engine-3.5 MERGED engine: Enhance the xml-rpc Long support to deal with Maps and Lists Never
oVirt gerrit 35353 0 ovirt-engine-3.5 MERGED core: Push ioTune QoS info when hotplugging disk Never

Description Elad 2014-09-23 13:13:43 UTC
Created attachment 940429 [details]
Engine and vdsm logs

Description of problem:
When hotplugging a disk that has a non-default disk profile, the ioTune attribute is not passed in the hotplug call. 

Version-Release number of selected component (if applicable):
rhev3.5 vt3.1
rhevm-3.5.0-0.12.beta.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a new QOS rule for storage in the DC. Specify a value in bandwith or iops.
2. Attach the rule to a storage domain in the DC via the "storage" main tab in webadmin
3. Create a new VM with a disk attached. Pick the default disk profile (not the new one)  
4. Start the VM
5. Attach a new disk to the VM with the new disk profile



Actual results:

In the hotplug call, ioTune attribute is not passed. 

Thread-293::DEBUG::2014-09-23 16:08:35,216::vm::3876::vm.Vm::(hotplugDisk) vmId=`dfd358b0-fc92-4013-ac7d-673d238af30c`::Hotplug disk xml: <disk device="disk" snapshot="no" type="block">
        <source dev="/rhev/data-center/00000002-0002-0002-0002-00000000009d/2e174ed7-92b4-4d9a-9d36-04cbd3c58365/images/3c4aee1a-ed5b-4fa7-9017-aa444b38b1ac/54c517a3-2d1a-4246-b72e-91c5b605779f"/>
        <target bus="virtio" dev="vdd"/>
        <serial>3c4aee1a-ed5b-4fa7-9017-aa444b38b1ac</serial>
        <driver cache="none" error_policy="stop" io="native" name="qemu" type="raw"/>
</disk>

Expected results:
The ioTune attribute should be given to vdsm for hotplug disk like it does for CreateVM.

Additional info:
Engine and vdsm logs

Comment 1 Elad 2014-12-08 08:30:22 UTC
ioTune attribute is now included in hotplug disk while hotplugging a disk that has a profile:

Thread-2726::DEBUG::2014-12-08 10:05:00,520::__init__::469::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'VM.hotplugDisk' in bridge with {u'params': {u'vmId': u'c6bf4fdb-a33c-
46d3-9b5b-94e179769786', u'drive': {u'iface': u'virtio', u'format': u'cow', u'optional': u'false', u'volumeID': u'25d479bb-7ab5-4a84-8d4e-5558e766531a', u'imageID': u'21ee792e-d
ae3-4888-a94d-3245a6fe623a', u'specParams': {u'ioTune': {u'total_bytes_sec': 10485760}}, u'readonly': u'false', u'domainID': u'fd598696-6a4b-47ae-86f8-c8063dde5f68', u'deviceId'
: u'21ee792e-dae3-4888-a94d-3245a6fe623a', u'poolID': u'00000002-0002-0002-0002-0000000000cd', u'device': u'disk', u'shared': u'false', u'propagateErrors': u'off', u'type': u'di
sk'}}, u'vmID': u'c6bf4fdb-a33c-46d3-9b5b-94e179769786'}

Verified using rhev 3.5 vt13.1

Comment 2 Eyal Edri 2015-02-17 17:08:10 UTC
rhev 3.5.0 was released. closing.


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