[NETVIRT-435] extra routes connectivity test failing in vpnservice CSIT suite Created: 18/Jan/17 Updated: 13/Jun/17 Resolved: 13/Jun/17 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Carbon |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jamo Luhrsen | Assignee: | Shashidhar R |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7589 |
| Description |
|
The stateful sg CSIT job [0] has two failures that the learn [1] or transparent [2] [0] https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-mitaka-upstream-stateful-carbon/ |
| Comments |
| Comment by Jamo Luhrsen [ 18/Jan/17 ] |
|
below is a trimmed email exchange that might provide better context to the issue. Hi Shashidhar, Since this behavior is currently breaking a use case in CSIT for the stateful implementation, could you please open a bug and update when a fix is available? Thanks, ---- Hi Daya, Extra routes were not considered with ACL earlier; we will work on providing the fix. Thanks, ---- Hi Shashidhar, Thanks, ---- Hi Hanamant, You can use "allowed_address_pairs" parameter of Neutron port to specify additional IP/MAC pairs along with VM's fixed IP/MAC addresses. ACL will program all the required flows for ip/mac specified in "allowed_address_pairs" along with fixed ip/mac. Thanks, ---- Hi Aswin , I see that extra-route IP 50.1.1.2 (ex: 50.1.1.2 behind 10.1.1.3 in below testcase) is not programmed in Egress-ACL-Table. Hence a ICMP packet to 50.1.1.2 from 10.1.1.4 gets dropped. cookie=0x90111ab, duration=26.154s, table=36, n_packets=3, n_bytes=294, priority=5,tun_id=0x111ab actions=group:150007 Thank you, |
| Comment by Jamo Luhrsen [ 05/Apr/17 ] |
| Comment by Vivekanandan Narasimhan [ 06/Apr/17 ] |
|
The above link posted by Jamo i.e., : has been analyzed and the failure has been root-caused same as 7939. The fix for the same on stable/boron is waiting here: We should land them both into stable/boron and only then we should revisit this bug. |