Duplicate iSCSI initiators causing live migration failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description
===========
See c#2 for the actual issue here.
Steps to reproduce
==================
LiveAutoBlockMi
Expected result
===============
Both the test and cleanup pass without impacting libvirtd.
Actual result
=============
The test passes, cleanup locks up the single thread handling the libvirtd event loop in 6.0.0.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://
stable/xena and master
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
libvirt (6.0.0) and QEMU
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
N/A
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
Trunk ports.
Logs & Configs
==============
Initially discovered and discussed as part of https:/
tags: | added: gate-failure |
description: | updated |
Changed in devstack: | |
status: | New → In Progress |
no longer affects: | nova |
i dont see how this can be related to trunk ports
with ml2/ovs trunk ports are implemeted using ovs bridges and patch ports in ovs
from a libvirt point of view the tap device is just attach to a different bridge with vlan tagging handeled entirly in ovs.
for ml2/ovn there is no visable differnce at teh libvirt level between a trunk port and a non trunk port. in both cases its just a tap device added directly to the br-int. in the trunk case openflow rules installed in the br-int handel the vlan tagging an striping so its entirly transparent to libvirt/qemu.
i suspect that this is just an unrelated failure that happens to occur in those test ratehr then beign casued by the use fo trunk ports. i dont know of any mechanium by which the use of trunk ports could impact libvirtd in any way so setting this to incomplete until we have a theroy as to how this could be related.