[NETVIRT-11] vxlan ports not created in clustered setup Created: 31/Mar/16  Updated: 09/Mar/18  Resolved: 01/Sep/16

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: Beryllium
Fix Version/s: None

Type: Bug
Reporter: Jamo Luhrsen Assignee: Anil Vishnoi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File logs1.tar.xz    
External issue ID: 5631

 Description   

setup:

3 controller nodes housing openstack control services as well as opendaylight with odl-ovsdb-openstack running in a cluster.

2 compute nodes

VIP via haproxy is used for interacting with openstack services (e.g. nova, neutron).

vxlan ports should be created when subnets are created, but this is not
happening. At this point, I have checked with a non-clustered setup and
did not see this issue. I also should note that with lots of poking
around (creating/deleting/restarting things) the vxlan ports will somehow
show up. I do not know the ultimate trigger for that.

the test I'm running is to bring up two openstack vm instances and verify
they can ping each other. With no underlay vxlan network, this is not
working. I do see the dhcp namespaces created on all three control nodes.
All the expected tap ports are also created.

There are also no flows programmed on the compute node br-int at this point, but
that could simply be a function of the vxlan ports not being created yet.

 Comments   
Comment by Jamo Luhrsen [ 05/Apr/16 ]

in a current reproduction I have two compute nodes (A and B). One VM instance was
created (after net/subnet creation). That instance ended up on compute node A. That
compute node only got one of the vxlan ports created so far (it's been aprox 1 hour).
compute node B (which does not have a VM, in case that matters) finally ended up with
all four expected vxlan ports. But, looking at ovs logs, you can see that these
ports are created with 1+ minute gaps.

compute node A:
-----------------------------------------------------------------------
[root@overcloud-novacompute-0 heat-admin]# virsh list
Id Name State
----------------------------------------------------
2 instance-00000003 running

[root@overcloud-novacompute-0 heat-admin]# ovs-vsctl show | grep Port
Port "vxlan-11.0.0.25"
Port "tap6530d6dc-56"
Port br-int
[root@overcloud-novacompute-0 heat-admin]# ovs-vsctl show | grep 'Port..vx'
Port "vxlan-11.0.0.25"
[root@overcloud-novacompute-0 heat-admin]#
[root@overcloud-novacompute-0 heat-admin]#
[root@overcloud-novacompute-0 heat-admin]#
[root@overcloud-novacompute-0 heat-admin]# virsh list
Id Name State
----------------------------------------------------
2 instance-00000003 running

[root@overcloud-novacompute-0 heat-admin]# ovs-vsctl show | grep 'Port..vx'
Port "vxlan-11.0.0.25"
[root@overcloud-novacompute-0 heat-admin]# egrep vxlan /var/log/openvswitch/*
/var/log/openvswitch/ovs-vswitchd.log:2016-04-05T22:49:14.343Z|00407|bridge|INFO|bridge br-int: added interface vxlan-11.0.0.25 on port 1
[root@overcloud-novacompute-0 heat-admin]#

compute node B:
-----------------------------------------------------------------------
[root@overcloud-novacompute-1 heat-admin]# virsh list
Id Name State
----------------------------------------------------

[root@overcloud-novacompute-1 heat-admin]# ovs-vsctl show | grep 'Port..vx'
Port "vxlan-11.0.0.24"
Port "vxlan-11.0.0.25"
Port "vxlan-11.0.0.21"
Port "vxlan-11.0.0.22"
[root@overcloud-novacompute-1 heat-admin]# egrep vxlan /var/log/openvswitch/*
/var/log/openvswitch/ovs-vswitchd.log:2016-04-05T22:49:14.478Z|00418|bridge|INFO|bridge br-int: added interface vxlan-11.0.0.25 on port 1
/var/log/openvswitch/ovs-vswitchd.log:2016-04-05T22:50:21.066Z|00420|bridge|INFO|bridge br-int: added interface vxlan-11.0.0.22 on port 2
/var/log/openvswitch/ovs-vswitchd.log:2016-04-05T22:50:41.955Z|00422|bridge|INFO|bridge br-int: added interface vxlan-11.0.0.21 on port 3
/var/log/openvswitch/ovs-vswitchd.log:2016-04-05T22:52:45.642Z|00425|bridge|INFO|bridge br-int: added interface vxlan-11.0.0.24 on port 4
[root@overcloud-novacompute-1 heat-admin]#

Comment by Jamo Luhrsen [ 06/Apr/16 ]

four log files with DEBUG logging enabled. They span a period of
time when compute node B only had 3 vxlan ports (log #19) and when it finally
got it's 4th port (log #16).

Comment by Jamo Luhrsen [ 06/Apr/16 ]

Attachment logs1.tar.xz has been added with description: karaf logs

Comment by Prashanth Jakkam [ 01/Sep/16 ]

This bug has been addressed as part of #5376.

We have tested with latest distribution after below patches were merged

https://git.opendaylight.org/gerrit/#/c/43580/
https://git.opendaylight.org/gerrit/#/c/44374/

Issue was not observed during multiple runs and observed, vxlan ports were created.

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