Comment 5 for bug 1881041

I believe there is some downstream work going on for the same issue. It appears the downstream tests worked for non-dvr. I have also tried this and can see that it does indeed work if DVR is disabled. Which makes sense given the comments in that patch. But for anyone else who finds this bug. This is what my environment looks like after disabling DVR

router 947f8372-e9bf-4a30-8f8f-7d0c73e30983 (neutron-15c1b81d-b833-4d34-b622-4c6a0bd6c0d7) (aka infra_r1)
    port lrp-65a28088-761c-461c-912c-7d0a3781ab6b
        mac: "fa:16:3e:69:fa:b0"
        networks: ["192.168.10.1/24"]
    port lrp-e696d78b-13c4-4781-8bd5-f6a7db16daee
        mac: "fa:16:3e:0a:c9:40"
        networks: ["172.20.10.118/16"]
        gateway chassis: [a3dfd16b-f743-4258-ab8e-513309166e4e]
    nat a3fa9ffa-7fd6-446a-afd7-5766d6ebc62c
        external ip: "172.20.10.118"
        logical ip: "192.168.10.0/24"
        type: "snat"
    nat d86c6d21-05f0-471a-8315-8c6b78b7bc3c
        external ip: "172.20.10.107"
        logical ip: "192.168.10.102"
        type: "dnat_and_snat"

The Gateway chassis specified:

Chassis "a3dfd16b-f743-4258-ab8e-513309166e4e"
    hostname: overcloud-controller-0.localdomain
    Encap geneve
        ip: "172.16.0.225"
        options: {csum="true"}
    Port_Binding cr-lrp-e696d78b-13c4-4781-8bd5-f6a7db16daee

[fedora@fedora-test ~]$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=15.6 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=9.82 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=8.70 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=9.25 ms

So to workaround the issue with tripleo:

parameter_defaults:
  NeutronEnableDVR: false