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-113 netvirt <p>The CSIT jobs for clustering (L2) failed in one ping for one of the instances. When we analyzed the flow entries observed that the tunnel entry to reach sone instance was not getting added in one of the compute nodes.</p> <p>Tunnel Flow entries are added to table:110 termed as Unicast entries per VM instance.</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-113

Tunnel Flow Entry Failed to be added in one compute Node leading to VM instance Ping Failure

Bug Resolved Cannot Reproduce Bertrand Low Venkatrangan Govindarajan Wed, 31 Aug 2016 19:45:13 +0000 Fri, 9 Mar 2018 18:21:30 +0000 Mon, 19 Sep 2016 08:53:22 +0000 Boron 0 7 <p>Attachment log.zip has been added with description: Log.html from the sandbox run</p> <p>Attachment odl1_karaf.zip has been added with description: ODL1 Logs</p> <p>Attachment odl2_karaf.zip has been added with description: ODL2 Logs</p> <p>Attachment odl3_karaf.zip has been added with description: ODL3 Logs</p> <p>the log.html added is a unique one which records the flow entries in all the openstack nodes. the setup had 3 Openstack nodes. one control and 2 compute nodes. the VM's always get created in only the compute nodes.</p> <p>Please let me know if any other explanation is needed on this bug.</p> <p>This bug is not reproducible. The attached logs from the sandbox run show that in the non-failover L2 tests, the VMs can be pinged but ssh does not work. This could indicate some temporary network issues that occurred during this particular sandbox run.</p> <p>The logs do not conclusively indicate a root cause.</p> <p>Closed due to bug not being reproducible and attached-logs being inconclusive.</p> <p>This issue was fixed in <a href="https://bugs.opendaylight.org/show_bug.cgi?id=6666" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=6666</a></p> <p>The <a href="https://jira.opendaylight.org/browse/NETVIRT-123" title="Interface with 0 DPN ID is created in ELan model" class="issue-link" data-issue-key="NETVIRT-123"><del>NETVIRT-123</del></a> and the patch for the <a href="https://jira.opendaylight.org/browse/NETVIRT-123" title="Interface with 0 DPN ID is created in ELan model" class="issue-link" data-issue-key="NETVIRT-123"><del>NETVIRT-123</del></a> is about new NetVirt. On the other hand, this bug report (<a href="https://jira.opendaylight.org/browse/NETVIRT-113" title="Tunnel Flow Entry Failed to be added in one compute Node leading to VM instance Ping Failure" class="issue-link" data-issue-key="NETVIRT-113"><del>NETVIRT-113</del></a>) is about the Legacy NetVirt. Therefore, I don't think this bug is a duplicate of <a href="https://jira.opendaylight.org/browse/NETVIRT-123" title="Interface with 0 DPN ID is created in ELan model" class="issue-link" data-issue-key="NETVIRT-123"><del>NETVIRT-123</del></a>. So I've reverted the Resolution from DUPLICATE to WORKSFORME.</p> <p>This update was done as a result of the link between the bugs..<br/> It shouldn't have affect this ticket.</p> Development External issue ID 6601 External issue URL Priority Rank 0|i01psn: