Description of problem:
Customer migrated an instance from one compute node to another and the network was not notified about the move of the MAC address.
They captured the traffic on the outgoing bond interface and there were not RARP packets at all. On RHOSP 13 they saw 5x RARP packets after every live migration.
On some further investigation they started capturing traffic on each possible location between the instance and the outgoing interface on the destination compute node:

* tap: 5x RARP packets were seen
* qbr: 5x RARP packets were seen
* qvb: 5x RARP packets were seen
* qvo: 5x RARP packets were seen
* br-int: -
* br-link: No RARP packets were seen

Afterwards, it was clear that "br-link" drops the corresponding RARP packets. Therefore, they repeated the test and started checking the OpenFlow rules of "br-link" on the destination compute node (the compute node was empty). According to the outputs, the RARP packets were correctly generated and sent out but the required OpenFlow rules were not present and therefore, the RARP packets were dropped. More information on how they tracked that on the next comment as private (contains customer sensitive data).


Version-Release number of selected component (if applicable):
openvswitch2.11-2.11.0-50.el8fdp.x86_64
openvswitch-selinux-extra-policy-1.0-22.el8fdp.noarch
rhosp-openvswitch-2.11-0.6.el8ost.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Logs on supportshell under '/cases/02710209/'