Description of problem: Prevent SR-IOV / direct port from being attached to neutron router (DVR or not) as packets are getting duplicated when added to the DVR router (or not) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deployed env with SR-IOV and DVR 2. Create net1, subnet 3. Create net2, subnet 4. Create DVR router, set gatawey, add interface for both nets 5. Create sr-iov port in net1 (port_sriov_1) 6. Create sr-iov port in net2 (port_sriov_2) 7. Boot ubuntu vm1 with port port_sriov_1 8. Boot ubuntu vm 2with port port_sriov_2 9. Associate floating for vm1 10. Ping from vm1 8.8.8.8, ping vm2 by floating Actual results: Packets are duplicated: ubuntu@vm-ew-1:~$ ping 10.1.2.6 PING 10.1.2.6 (10.1.2.6) 56(84) bytes of data. 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.312 ms 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!) 64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!) ubuntu@vm-ew-1:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!) 64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!) 64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!) 64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=4.36 ms Expected results: Packets should not be duplicated Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0935