Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2103688

Summary: [OSP16.1] Mac-address change causing lost of traffic
Product: Red Hat OpenStack Reporter: ggrimaux
Component: python-networking-ovnAssignee: OSP Team <rhos-maint>
Status: CLOSED NOTABUG QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16.1 (Train)CC: apevec, jlibosva, lhh, majopela, scohen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 22:12:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description ggrimaux 2022-07-04 14:02:26 UTC
Description of problem:
Client live-migrated an instance 2 weeks ago.

We don't know yet why but the TAP port on the compute has the wrong mac-address:
50: tap09d0d2b2-04: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc fq_codel master ovs-system state UNKNOWN group default qlen 1000
    link/ether fe:16:3e:a7:a8:82 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:fea7:a882/64 scope link
       valid_lft forever preferred_lft forever

Notice the mac address start with FE ^


But in OVN the mac start with fa:
_uuid               : 1e549773-c535-452f-ae31-a15688bd7c2a
addresses           : ["fa:16:3e:a7:a8:82 10.12.2.127"]
port_security       : ["fa:16:3e:a7:a8:82 10.12.2.127 10.12.2.5 10.12.2.7"]


Port show  shows fa:
| mac_address             | fa:16:3e:a7:a8:82 

But the port is showing as DOWN.

Event the interface in virsh shows fa:
()[root@compute /]# virsh domiflist 18
 Interface        Type     Source   Model    MAC
----------------------------------------------------------------
 tap09d0d2b2-04   bridge   br-int   virtio   fa:16:3e:a7:a8:82


We need your help to bring back traffic to this port and understanding why the mac changed somehow.

Version-Release number of selected component (if applicable):
OSP16.1.6

How reproducible:
N/A Happened once

Steps to Reproduce:
1. N/A
2.
3.

Actual results:
Traffic is not working on that port.
Port is listed as DOWN.

Expected results:
Port is listed as UP.
Traffic work to the instance port.

Additional info:
Got sosreport from compute node.

Comment 1 Jakub Libosvar 2022-07-04 16:59:10 UTC
All MACs on compute nodes start with "fe" when the port mac is "fa". This is not a bug but it's designed as such to avoid kernel seeing two same mac addresses on different network endpoints.