https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-11 netvirt <p>setup:</p> <p>3 controller nodes housing openstack control services as well as opendaylight with odl-ovsdb-openstack running in a cluster.</p> <p>2 compute nodes</p> <p>VIP via haproxy is used for interacting with openstack services (e.g. nova, neutron).</p> <p>vxlan ports should be created when subnets are created, but this is not<br/> happening. At this point, I have checked with a non-clustered setup and<br/> did not see this issue. I also should note that with lots of poking<br/> around (creating/deleting/restarting things) the vxlan ports will somehow<br/> show up. I do not know the ultimate trigger for that.</p> <p>the test I'm running is to bring up two openstack vm instances and verify<br/> they can ping each other. With no underlay vxlan network, this is not<br/> working. I do see the dhcp namespaces created on all three control nodes.<br/> All the expected tap ports are also created.</p> <p>There are also no flows programmed on the compute node br-int at this point, but<br/> that could simply be a function of the vxlan ports not being created yet.</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-11

vxlan ports not created in clustered setup

Bug Resolved Done Anil Vishnoi Jamo Luhrsen Thu, 31 Mar 2016 00:55:34 +0000 Fri, 9 Mar 2018 18:21:29 +0000 Thu, 1 Sep 2016 13:09:38 +0000 Beryllium 0 3 <p>in a current reproduction I have two compute nodes (A and B). One VM instance was<br/> created (after net/subnet creation). That instance ended up on compute node A. That<br/> compute node only got one of the vxlan ports created so far (it's been aprox 1 hour).<br/> compute node B (which does not have a VM, in case that matters) finally ended up with<br/> all four expected vxlan ports. But, looking at ovs logs, you can see that these <br/> ports are created with 1+ minute gaps.</p> <p>compute node A:<br/> -----------------------------------------------------------------------<br/> <span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># virsh list<br/> Id Name State<br/> ----------------------------------------------------<br/> 2 instance-00000003 running</p> <p><span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># ovs-vsctl show | grep Port<br/> Port "vxlan-11.0.0.25"<br/> Port "tap6530d6dc-56"<br/> Port br-int<br/> <span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># ovs-vsctl show | grep 'Port..vx'<br/> Port "vxlan-11.0.0.25"<br/> <span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># <br/> <span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># <br/> <span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># <br/> <span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># virsh list<br/> Id Name State<br/> ----------------------------------------------------<br/> 2 instance-00000003 running</p> <p><span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># ovs-vsctl show | grep 'Port..vx'<br/> Port "vxlan-11.0.0.25"<br/> <span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># egrep vxlan /var/log/openvswitch/*<br/> /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<br/> <span class="error">&#91;root@overcloud-novacompute-0 heat-admin&#93;</span># </p> <p>compute node B:<br/> -----------------------------------------------------------------------<br/> <span class="error">&#91;root@overcloud-novacompute-1 heat-admin&#93;</span># virsh list<br/> Id Name State<br/> ----------------------------------------------------</p> <p><span class="error">&#91;root@overcloud-novacompute-1 heat-admin&#93;</span># ovs-vsctl show | grep 'Port..vx'<br/> Port "vxlan-11.0.0.24"<br/> Port "vxlan-11.0.0.25"<br/> Port "vxlan-11.0.0.21"<br/> Port "vxlan-11.0.0.22"<br/> <span class="error">&#91;root@overcloud-novacompute-1 heat-admin&#93;</span># egrep vxlan /var/log/openvswitch/*<br/> /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<br/> /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<br/> /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<br/> /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<br/> <span class="error">&#91;root@overcloud-novacompute-1 heat-admin&#93;</span>#</p> <p>four log files with DEBUG logging enabled. They span a period of<br/> time when compute node B only had 3 vxlan ports (log #19) and when it finally<br/> got it's 4th port (log #16).</p> <p>Attachment logs1.tar.xz has been added with description: karaf logs</p> <p>This bug has been addressed as part of #5376.</p> <p>We have tested with latest distribution after below patches were merged</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/43580/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/43580/</a><br/> <a href="https://git.opendaylight.org/gerrit/#/c/44374/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44374/</a></p> <p>Issue was not observed during multiple runs and observed, vxlan ports were created.</p> Development External issue ID 5631 External issue URL Rank 0|i01p5z: