[NETVIRT-560] CSIT Sporadic failures - ssh to instance from control node dhcp namespace failed Created: 22/Mar/17  Updated: 06/Jul/17  Resolved: 06/Jul/17

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

Type: Bug
Reporter: Jamo Luhrsen Assignee: Koby Aizer
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


External issue ID: 8052

 Description   

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

NOTE, this same procedure worked before this test case on 5 other instances.



 Comments   
Comment by Jamo Luhrsen [ 22/Mar/17 ]

similar failure:

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

Comment by Koby Aizer [ 23/Mar/17 ]

Failure is caused due to a missing table=21 rules for the private IP of the SNAT VM.
This is probably a duplicate of bugs 7939/7938/7968/7997

Comment by Vivekanandan Narasimhan [ 04/Apr/17 ]

Hi Koby/Jamo,

I went through this link again:

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

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.

So this connectivity never uses Table 21 at all and so this issue is not a duplicate of table 21 related problems.

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.

The same is the case with 1st link in this bug as well:
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

So, I request you both to decide on this one.

Vivek

Comment by Periyasamy Palanisamy [ 04/Apr/17 ]

These CSIT results are quite old. Shall we look at latest csit reports if there is same pattern of failures for ELAN ?

Comment by Koby Aizer [ 05/Apr/17 ]

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?

Comment by Jamo Luhrsen [ 06/Apr/17 ]

(In reply to Koby Aizer from comment #5)
> 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?

let's close this as fixed if it doesn't show up in the next week or
so. I do not recall seeing it for a while now.

Comment by Jamo Luhrsen [ 11/Apr/17 ]

another similar failure:

https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-1node-openstack-newton-upstream-stateful-boron/372/archives/log.html.gz#s1-s1-s2-t22

Comment by Periyasamy Palanisamy [ 12/Apr/17 ]

This (/372) report seems to be L3 failure. Vivek, Can you triage it and let us know what is wrong ?

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