[GENIUS-175] vlan member interface creation fails in netvirt 3 node CSIT Created: 11/Jul/18  Updated: 17/Jul/18  Resolved: 17/Jul/18

Status: Verified
Project: genius
Component/s: General
Affects Version/s: None
Fix Version/s: Oxygen-SR3, Fluorine

Type: Bug Priority: Medium
Reporter: Faseela K Assignee: Faseela K
Resolution: Done Votes: 0
Labels: csit, csit:3node, csit:failures, csit:sporadic
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Clustering Stability

 Description   

netvirt 3 node l2 suite randomly fails on VMs failing to get IP :

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/builder-copy-sandbox-logs/183/faseelanetvirt-csit-3node-openstack-queens-upstream-stateful-fluorine/39/

The IPs are not getting assigned only for network-type-vlan.

And while troubleshooting, it was seen that table 0 entry in the openstack controller node is not proper.

The flow entry corresponding to interface 150501453275533:br-physnet1-pa:1121 is missing.

Also, the corresponding interface is not present in the operational interface DS.

 Comments   
Comment by Sam Hague [ 12/Jul/18 ]

from k.faseela

When a trunk port, and a trunk-member is created back to back,
there is a race condition in interface-manager that the trunk member
tries to fetch the interface-state information for the trunk,
and it fails, as trunk-interface-state is parallelly getting updated.
With Job Coordinator, this works properly in single node, but when
3 node comes, the synchronization is not at all valid.

The fix uses DataTreeEventCallBackRegistrar to delay the vlan-member
interface configuration till interface-state for vlan-trunk shows up.

Generated at Wed Feb 07 20:00:06 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.