SR-IOV. After migration/evacuation of an instance, its MAC is not cleaned up from the source node

Bug #1700702 reported by Alexander Rubtsov on 2017-06-27
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Medium
MOS Nova
9.x
Medium
MOS Nova

Bug Description

--- Environment ---
MOS: 9.2+
Features: SR-IOV

--- Description ---
After migration/evacuation of an instance, its MAC is not cleaned up from the corresponding VF in the source node.

--- Steps to reproduce ---
(a sample of reproduction attempt is attached)
1) Build an environment with SR-IOV support and at least 2 compute nodes
2) Create an SR-IOV Neutron port
3) Spin up a VM instance connected to this Neutron port
4) Determine the compute node that hosts this instance
5) In this Compute node check MAC-addresses associated to VFs of the corresponding physical NIC
6) Mark this Compute node as disabled
7) Evacuate the instance to another Compute node
8) Repeat the step #5 on the same node

--- Actual result ---
The MAC-address is still associated to VF

--- Expected result ---
The MAC-address has been cleaned up

Alexander Rubtsov (arubtsov) wrote :
Changed in mos:
assignee: nobody → MOS Nova (mos-nova)
Alexander Rubtsov (arubtsov) wrote :

sla2 for 9.0-updates

Vladyslav Drok (vdrok) wrote :

Thanks for the bug report. Does it actually cause any issues? In code I see the following -- https://github.com/openstack/nova/blob/45dfc7106ebb95bacc2464ff37f372aae785691d/nova/virt/libvirt/vif.py#L873-L875. The same bit is present in mitaka.

Alexander Rubtsov (arubtsov) wrote :

Vladyslav,

I'm in progress of clarifying the impact with the customer.

Alexander Rubtsov (arubtsov) wrote :

The customer has confirmed that the reported behavior doesn't have impact on migration/evacuation.

Vladyslav Drok (vdrok) on 2017-07-05
Changed in mos:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments