[OVSDB-380] vxlan ports in Configuration datastore not created on device Created: 21/Oct/16  Updated: 19/Oct/17  Resolved: 22/Feb/17

Status: Resolved
Project: ovsdb
Component/s: Clustering
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Venkatrangan Govindarajan Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Zip Archive odl1.zip     Zip Archive odl2.zip     Zip Archive odl3.zip     Text File ownership_info.txt     Text File topology_config.txt     Text File topology_operational.txt    
External issue ID: 7005

 Description   

Used Legacy Netvirt and stacked up 3 openstack nodes. Then performed operations like create Network/Subnet and instances.

At the end of operations, the instances failed to participate in communication. then noticed that it was not a full mesh.

From the output of ovs-vsctl show we notice that the vxlan ports in compute nodes are not connecting to control node.

sudo ovs-vsctl show in various nodes
[gvrangan@controlnode devstack]$ sudo ovs-vsctl show
ed3798b7-0094-491c-bdd6-e8fdf7821bea
Manager "tcp:10.128.0.3:6640"
is_connected: true
Manager "tcp:10.128.0.9:6640"
is_connected: true
Manager "tcp:10.128.0.7:6640"
is_connected: true
Bridge br-int
Controller "tcp:10.128.0.9:6653"
is_connected: true
Controller "tcp:10.128.0.7:6653"
is_connected: true
Controller "tcp:10.128.0.3:6653"
is_connected: true
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "vxlan-10.128.0.5"
Interface "vxlan-10.128.0.5"
type: vxlan
options:

{key=flow, local_ip="10.128.0.4", remote_ip="10.128.0.5"}

Port "vxlan-10.128.0.6"
Interface "vxlan-10.128.0.6"
type: vxlan
options:

{key=flow, local_ip="10.128.0.4", remote_ip="10.128.0.6"}

Port "tap89b1db3d-ef"
Interface "tap89b1db3d-ef"
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
ovs_version: "2.5.0"

compute1

[gvrangan@compute2 devstack]$ sudo ovs-vsctl show
9ed900aa-b573-4fc8-9ae1-c2889c638fff
Manager "tcp:10.128.0.3:6640"
is_connected: true
Manager "tcp:10.128.0.7:6640"
is_connected: true
Manager "tcp:10.128.0.9:6640"
is_connected: true
Bridge br-int
Controller "tcp:10.128.0.9:6653"
is_connected: true
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "vxlan-10.128.0.5"
Interface "vxlan-10.128.0.5"
type: vxlan
options:

{key=flow, local_ip="10.128.0.6", remote_ip="10.128.0.5"}

Port "tap8dca1a92-2c"
Interface "tap8dca1a92-2c"
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
ovs_version: "2.5.2"

compute 2

gvrangan@compute1 devstack]$ sudo ovs-vsctl show
795fa0e8-b4b2-49ee-b562-a2137f1bd585
Manager "tcp:10.128.0.3:6640"
is_connected: true
Manager "tcp:10.128.0.9:6640"
is_connected: true
Manager "tcp:10.128.0.7:6640"
is_connected: true
Bridge br-int
Controller "tcp:10.128.0.9:6653"
is_connected: true
Controller "tcp:10.128.0.3:6653"
is_connected: true
Controller "tcp:10.128.0.7:6653"
is_connected: true
fail_mode: secure
Port "vxlan-10.128.0.6"
Interface "vxlan-10.128.0.6"
type: vxlan
options:

{key=flow, local_ip="10.128.0.5", remote_ip="10.128.0.6"}

Port br-int
Interface br-int
type: internal
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
ovs_version: "2.5.2"

 Comments   
Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

checked the config datastore and identified that the ports are added by NEtvirt. but not found in operational. so I feel the ovsdb southbound failed to write to device.

Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

Attachment odl3.zip has been added with description: ODL3 logs

Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

Attachment odl1.zip has been added with description: odl1 logs

Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

Attachment odl2.zip has been added with description: odl2 logs

Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

Attachment ownership_info.txt has been added with description: entity_owners

Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

Attachment topology_config.txt has been added with description: Config topology

Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

Attachment topology_operational.txt has been added with description: Operational topology from device

Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

Other details

odl1 : 10.128.0.3 (member-1)
odl2: 10.128.0.7 (member-2)
odl3 : 10.128.0.9 (member-3)

Comment by Anil Vishnoi [ 21/Oct/16 ]

Venkat, which branch are you using ?

Comment by Venkatrangan Govindarajan [ 21/Oct/16 ]

(In reply to Anil Vishnoi from comment #9)
> Venkat, which branch are you using ?

stable/boron, sorry for not mentioning it.

Comment by Vinh Nguyen [ 21/Oct/16 ]

The log shows the following Exception after the compute node is restarted. The exception are quite similar to the one in bug https://bugs.opendaylight.org/show_bug.cgi?id=6944

Caused by: org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1}

]/node/node[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb://uuid/9ed900aa-b573-4fc8-9ae1-c2889c638fff}

]/AugmentationIdentifier

{childNames=[(urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)managed-node-entry, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)connection-info, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)openvswitch-external-ids, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)openvswitch-other-configs, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)ovs-version, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)interface-type-entry, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)db-version, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)queues, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)manager-entry, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)datapath-type-entry, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)qos-entries, (urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)autoattach]}

/(urn:opendaylight:params:xml:ns:yang:ovsdb?revision=2015-01-05)manager-entry does not exist. Cannot apply modification to its children.

Comment by Vinh Nguyen [ 26/Oct/16 ]

This problem cannot be reproduced in my testing.
From the attached, after re-stacking compute-node2 only connected to ODL3 as reflected in the config datastore:

{
"node-id": "ovsdb://uuid/9ed900aa-b573-4fc8-9ae1-c2889c638fff/bridge/br-int",
...
"ovsdb:controller-entry": [

{ "target": "tcp:10.128.0.9:6653" }

],
...}

Comment by Anil Vishnoi [ 02/Feb/17 ]

Hi Venkat,

Do you still face this issue in your setup? If not, can you please close this bug.If you still see this issue, are you running the latest stable/boron branch?

Comment by Anil Vishnoi [ 22/Feb/17 ]

Closing this bug, if you see the issue again please re-open the bug and provide all the required logs.

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