contrail 3.2.0.0-19 + Mirantis Mitaka : with TSN some Qfx interfaces are not configured though OVSDB
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.2 |
Fix Committed
|
High
|
Hari Prasad Killi | |||
R4.0 |
Fix Committed
|
High
|
Hari Prasad Killi | |||
Trunk |
Fix Committed
|
High
|
Hari Prasad Killi |
Bug Description
Customer : Citrix
JTAC case : 2017-0522-0857
Customer has Qfx (Virtual chassis fabric) that is used as a TOR.
He added xe-3/0/4.0 to contrail and this interface gets setup on the TOR (QFX). The BM host is able to get DHCP lease.
He then added xe-3/0/5.0 to contrail and this interface does NOT get setup on the TOR. (show configuration interfaces xe-3/0/5 doesn't have anything)
Interestingly if he deletes above two interfaces and adds xe-3/0/5 interface first and then xe-3/0/4 issue is not seen. He is easily able to replicate this.
=======
root@lab-qfx> show configuration interfaces xe-3/0/5
description compute6;
{master:0}
root@lab-qfx>
{master:0}
root@lab-qfx>
{master:0}
root@lab-qfx> show ovsdb interface
Interface VLAN ID Bridge-domain
ge-2/0/6
ge-2/0/7
xe-3/0/4 0 Contrail-
xe-3/0/5
{master:0}
root@lab-qfx> show ovsdb interface
Interface VLAN ID Bridge-domain
ge-2/0/6
ge-2/0/7
xe-3/0/4 0 Contrail-
xe-3/0/5
{master:0}
root@lab-qfx> show configuration interfaces xe-3/0/5
description compute6;
{master:0}
root@lab-qfx> show configuration interfaces xe-3/0/5
description compute6;
{master:0}
root@lab-qfx> ...s Contrail-
interface xe-3/0/4.0;
vxlan {
vni 5;
}
=======
- We looked at the contrail logs (/var/log/contrail/ on TSN) but it doesn't have much info.
- We also looked at the TSN introspect page - property OvsdbVlanPortBi
- There were no ovsdb commit failures on Qfx.
- It seems like the ovsdb config for xe-3/0/5 interface is not even pushed to the TOR.
I have collected below info :
/var/log/contrail from TSN node
ovsdb traceoptions from Qfx
Qfx RSI
Data uploaded at:
ftp://ftp.
description: | updated |
information type: | Proprietary → Public |
tags: | added: 2017-0522-0857 jtac |
tags: |
added: jtac-p3 removed: jtac |
For xe-3/0/5 interface (Which config not getting pushed to QFX) observed the following log in Sandesh Trace of OVSDB.
Required logical interface is getting created at API server. Buy no vlan port binding is observed on obsdb introspect.
Sandesh Trace (Ovsdb ------- ------) global- system- config: lab-qfx: xe-3/0/ 5:xe-3/ 0/5.100 file = controller/ src/vnsw/ agent/ovs_ tor_agent/ ovsdb_client/ vlan_port_ binding_ ovsdb.cc line = 278 global- system- config: lab-qfx: xe-3/0/ 5:xe-3/ 0/5.100 file = controller/ src/vnsw/ agent/ovs_ tor_agent/ ovsdb_client/ vlan_port_ binding_ ovsdb.cc line = 293
-------
2017-05-25 15:51:25.424 OvsdbTrace: log = VM Interface Unavialable, Ignoring Logical Port default-
2017-05-25 15:51:25.427 OvsdbTrace: log = Ignoring Port Vlan Binding due to device name unavailablity Logical port = default-