Comment 0 for bug 1693052

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.

=====================================From customers Qfx========================================
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-90ff4126-a7f8-42f1-adec-6dd58fb5c978
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-90ff4126-a7f8-42f1-adec-6dd58fb5c978
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-90ff4126-a7f8-42f1-adec-6dd58fb5c978
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 OvsdbVlanPortBindingResp . It just shows xe-3/0/4 interface.
- 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.juniper.net/pub/incoming/2017-0522-0857/