[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 |
||
| External issue ID: | 8052 |
| Description |
|
NOTE, this same procedure worked before this test case on 5 other instances. |
| Comments |
| Comment by Jamo Luhrsen [ 22/Mar/17 ] |
|
similar failure: |
| 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. |
| Comment by Vivekanandan Narasimhan [ 04/Apr/17 ] |
|
Hi Koby/Jamo, I went through this link again: 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: 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) let's close this as fixed if it doesn't show up in the next week or |
| Comment by Jamo Luhrsen [ 11/Apr/17 ] |
|
another similar failure: |
| 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 ? |