tempest.api.volume.test_volumes_extend.VolumesExtendAttachedTest.test_extend_attached_volume failing when using the Q35 machine type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Medium
|
Alexandre arents |
Bug Description
Description
===========
tempest.
DNM: Run tempest-full-py3 with q35 machine type
https:/
libvirtd appears to be receiving a DEVICE_DELETED event from QEMU just after the SCSI rescan and well before we attempt to block resize the disk within the domain:
Instance UUID: b3b8394a-
Domain name: instance-00000055
We currently end up waiting for 12 seconds here as os-brick is attempting to find a mpath device, even when use_multipath=
find_multipath_
https:/
FWIW this works around the issue locally for me by calling for a block resize before QEMU has a chance to raise the DELETED_DEVICE notification to libvirtd.
Steps to reproduce
==================
* Use the Q35 machine type
[libvirt]
* Run the test_extend_
$ tempest run --regex tempest.
Expected result
===============
Test passes.
Actual result
=============
Test fails.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://
1316c1c2850d
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
Libvirt + KVM
qemu-system-x86 1:2.11+
libvirt0:amd64 4.0.0-1ubuntu8.10
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
LVM/iSCSI
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
N/A
Logs & Configs
==============
2019-06-09 14:51:08.215+0000: 22679: debug : qemuMonitorJSON
Jun 09 14:51:20.840546 ubuntu-
summary: |
tempest.api.volume.test_volumes_extend.VolumesExtendAttachedTest.test_extend_attached_volume - failing when usinug the Q35 machine type + failing when using the Q35 machine type |
tags: | added: libvirt |
tags: | added: qemu volumes |
Changed in nova: | |
status: | Triaged → Invalid |
Is the plan to just get https:/ /review. opendev. org/#/c/ 664418/ released and bump nova's minimum required version of os-brick that it depends on and consider this nova bug fixed? Or are there nova changes to make as well?