[NETVIRT-527] CSIT Sporadic failures - tempest.scenario.test_network_advanced_server_ops.TestNetworkAdvancedServerOps.test_server_connectivity_rebuild Created: 13/Mar/17 Updated: 25/May/18 Resolved: 25/May/18 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Oxygen, Fluorine |
| Fix Version/s: | Oxygen-SR2, Fluorine |
| Type: | Bug | Priority: | Highest |
| Reporter: | Jamo Luhrsen | Assignee: | Aswin Suryanarayanan |
| Resolution: | Done | Votes: | 0 |
| Labels: | csit:failures, csit:snat-conntrack, csit:sporadic | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7967 |
| Description |
|
|
| Comments |
| Comment by Alon Kochba [ 14/Mar/17 ] |
|
Note that networking-odl_v1 had some known floating IP issues, please update here if this is seen for v2 as well. Koby can probably confirm if this is a different issue through the model dumps |
| Comment by Koby Aizer [ 15/Mar/17 ] |
|
This looks like a different issue - I can't tell from the model dumps as this is a tempest test that deletes the configuration before the dump. However, from the q-svc.log I can see that the floatingip information was synced correctly, and this doesn't sound like the known v1 floating ip bug. |
| Comment by Jamo Luhrsen [ 25/Apr/17 ] |
|
tempest failures appear to mostly have been resolved. We can re-open any |
| Comment by Jamo Luhrsen [ 03/May/17 ] |
| Comment by Jamo Luhrsen [ 18/Jul/17 ] |
| Comment by Jamo Luhrsen [ 27/Sep/17 ] |
|
no longer seen in CSIT |
| Comment by Jamo Luhrsen [ 20/Mar/18 ] |
|
still there in our snat-conntrack job with the Oxygen candidate release: |
| Comment by Sam Hague [ 06/Apr/18 ] |
|
Stiller there: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-openstack-queens-upstream-stateful-snat-conntrack-oxygen/232/ |
| Comment by Aswin Suryanarayanan [ 25/May/18 ] |
|
[1] have removed stale flows which was causing the issue in conntrack job. |