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-560 netvirt <p><a href="https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-boron/258/archives/log.html.gz#s1-s1-s1-t20-k2" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-boron/258/archives/log.html.gz#s1-s1-s1-t20-k2</a></p> <p>NOTE, this same procedure worked before this test case on 5 other instances.</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-560

CSIT Sporadic failures - ssh to instance from control node dhcp namespace failed

Bug Resolved Cannot Reproduce Koby Aizer Jamo Luhrsen Wed, 22 Mar 2017 21:18:53 +0000 Thu, 6 Jul 2017 01:05:59 +0000 Thu, 6 Jul 2017 01:05:59 +0000 Carbon General 0 5 <p>similar failure:</p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-carbon/237/archives/log.html.gz#s1-s1-s1-t18" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-carbon/237/archives/log.html.gz#s1-s1-s1-t18</a></p> <p>Failure is caused due to a missing table=21 rules for the private IP of the SNAT VM.<br/> This is probably a duplicate of bugs 7939/7938/7968/7997</p> <p>Hi Koby/Jamo,</p> <p>I went through this link again:</p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-carbon/237/archives/log.html.gz#s1-s1-s1-t18" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-carbon/237/archives/log.html.gz#s1-s1-s1-t18</a></p> <p>And I could see that this is L2 Connectivity test failing and not L3 Connectivity Test. SSH'ing from 40.0.0.2 to 40.0.0.8 is failing.</p> <p>So this connectivity never uses Table 21 at all and so this issue is not a duplicate of table 21 related problems.</p> <p>So we need to either re-triage this from ELAN perspective (or) we can close this bug (since many fixes went into ELAN last week) and re-open if hte problem comes back.</p> <p>The same is the case with 1st link in this bug as well:<br/> <a href="https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-boron/258/archives/log.html.gz#s1-s1-s1-t20-k2" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-boron/258/archives/log.html.gz#s1-s1-s1-t20-k2</a></p> <p>So, I request you both to decide on this one.</p> <p>Vivek</p> <p>These CSIT results are quite old. Shall we look at latest csit reports if there is same pattern of failures for ELAN ?</p> <p>Yeah I think we shouldn't look into those old failures, as many fixes went it since then. I think that in Jamo's last mail there are still failures like that - but all of them in Boron - so maybe those are patches that weren't merged yet?</p> <p>(In reply to Koby Aizer from comment #5)<br/> &gt; Yeah I think we shouldn't look into those old failures, as many fixes went<br/> &gt; it since then. I think that in Jamo's last mail there are still failures<br/> &gt; like that - but all of them in Boron - so maybe those are patches that<br/> &gt; weren't merged yet?</p> <p>let's close this as fixed if it doesn't show up in the next week or<br/> so. I do not recall seeing it for a while now.</p> <p>another similar failure:</p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-boron/372/archives/log.html.gz#s1-s1-s2-t22" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-boron/372/archives/log.html.gz#s1-s1-s2-t22</a></p> <p>This (/372) report seems to be L3 failure. Vivek, Can you triage it and let us know what is wrong ?</p> Development External issue ID 8052 External issue URL Rank 0|i01sjz: Status Whiteboard csit:sporadic_failures