contrail 3.2.0.0-19 + Mirantis Mitaka : with TSN some Qfx interfaces are not configured though OVSDB

Bug #1693052 reported by Himanshu
12
This bug affects 2 people
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.

=====================================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/

Himanshu (bhimanshu)
description: updated
Revision history for this message
chhandak (chhandak) wrote :

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
--------------------)
2017-05-25 15:51:25.424 OvsdbTrace: log = VM Interface Unavialable, Ignoring Logical Port default-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
2017-05-25 15:51:25.427 OvsdbTrace: log = Ignoring Port Vlan Binding due to device name unavailablity Logical port = default-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

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R3.2

Review in progress for https://review.opencontrail.org/32670
Submitter: Hari Prasad Killi (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/32676
Submitter: Hari Prasad Killi (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/32670
Committed: http://github.com/Juniper/contrail-controller/commit/abfc3c013f17d351b27a4d681afb7ae7ae5f190b
Submitter: Zuul (<email address hidden>)
Branch: R3.2

commit abfc3c013f17d351b27a4d681afb7ae7ae5f190b
Author: Hari Prasad Killi <email address hidden>
Date: Thu Jun 8 23:35:54 2017 +0530

Update the correct metadata name.

Modify to fetch the physical router from the node adjacent to physical
interface, instead of getting it from the link table.

Change-Id: Icb159a74ab73e9acc808b0b7aa73ef4c83da6093
closes-bug: #1693052

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R4.0

Review in progress for https://review.opencontrail.org/32864
Submitter: Hari Prasad Killi (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/32676
Committed: http://github.com/Juniper/contrail-controller/commit/03419046a4aaa50039436b13ac2c604b01aae174
Submitter: Zuul (<email address hidden>)
Branch: master

commit 03419046a4aaa50039436b13ac2c604b01aae174
Author: Hari Prasad Killi <email address hidden>
Date: Fri Jun 9 00:11:42 2017 +0530

Update the correct metadata name.

Modify to fetch the physical router from the node adjacent to physical
interface, instead of getting it from the link table.

Change-Id: I0ee59c4a17a97e3ef6728ce3e5700e9eb7706000
closes-bug: #1693052

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/32864
Committed: http://github.com/Juniper/contrail-controller/commit/904b062e2e194fbc899be9066c6593a06022c667
Submitter: Zuul (<email address hidden>)
Branch: R4.0

commit 904b062e2e194fbc899be9066c6593a06022c667
Author: Hari Prasad Killi <email address hidden>
Date: Fri Jun 9 00:11:42 2017 +0530

Update the correct metadata name.

Modify to fetch the physical router from the node adjacent to physical
interface, instead of getting it from the link table.

Change-Id: I0ee59c4a17a97e3ef6728ce3e5700e9eb7706000
closes-bug: #1693052

information type: Proprietary → Public
Himanshu (bhimanshu)
tags: added: 2017-0522-0857 jtac
Himanshu (bhimanshu)
tags: added: jtac-p3
removed: jtac
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.