Comment 1 for bug 1802373

Revision history for this message
Daniel Alvarez (dalvarezs) wrote :

I've tried to reproduce locally the scenario that this test is exercising and it works good for me:

$ sudo ovn-nbctl show
switch 9bb2d9c0-831f-4527-ae97-6aec8b477f42 (neutron-448eee0d-f336-45aa-9b23-308235785569) (aka private)
    port 39e36b42-3d09-4e28-9bae-2d302a03481e
        type: localport
        addresses: ["fa:16:3e:01:f3:fa 10.0.0.2 fded:d86e:b73f:0:f816:3eff:fe01:f3fa"]
    port 367ac68a-9732-4c91-a458-2fc221491e2f
        type: router
        router-port: lrp-367ac68a-9732-4c91-a458-2fc221491e2f
    port 55edcb76-e904-4dea-8ddb-cb770c3b7aee
        type: router
        router-port: lrp-55edcb76-e904-4dea-8ddb-cb770c3b7aee
    port 51cebfef-39a7-4996-81e6-dd48a4a81dfd
        addresses: ["fa:16:3e:0c:84:d6 10.0.0.10 fded:d86e:b73f:0:f816:3eff:fe0c:84d6"]
switch 62370e9c-8078-4388-88e4-7bbb621fa574 (neutron-ef71d6ca-7640-45c1-aed3-e2b8cef15c28) (aka public)
    port 59f74080-ff5f-474d-9910-f362122d0ddf
        type: router
        router-port: lrp-59f74080-ff5f-474d-9910-f362122d0ddf
    port provnet-ef71d6ca-7640-45c1-aed3-e2b8cef15c28
        type: localnet
        addresses: ["unknown"]
    port 64c896a9-bea0-4a48-b96b-96464df28f3b
        type: localport
        addresses: ["fa:16:3e:c6:dd:fe"]
switch eebb15e4-4d2c-48ad-b19f-894e2c517c6c (neutron-a934cf7d-50f7-4dde-beb2-78cb180a0acc) (aka network2)
    port 184e0495-03f3-483e-b6fa-b978e9ec8905
        type: router
        router-port: lrp-184e0495-03f3-483e-b6fa-b978e9ec8905
    port 67d4135f-db47-45c8-bf1b-c4b0b7d6051b
        type: localport
        addresses: ["fa:16:3e:2f:75:ab 192.168.10.2"]
    port f451bd39-5d44-41e8-b8a4-1ebcc83147c9
        addresses: ["fa:16:3e:3a:41:fc 192.168.10.4"]
switch 6261c14d-c0da-4d2c-b309-16ce563761e0 (neutron-78286b7a-06b6-48b1-ab40-f87ccb23ac1d) (aka network3)
    port ed598f54-6519-4bed-b30c-483ed67878d2 (aka p32)
        type: router
        router-port: lrp-ed598f54-6519-4bed-b30c-483ed67878d2
    port 9e215eaa-e905-4ce9-af1d-ac5c6d2a3b8a (aka p31)
        addresses: ["fa:16:3e:4f:33:5c 192.168.30.7"]
    port 78bd0e86-44ea-4512-b03e-743bb33d877f
        type: localport
        addresses: ["fa:16:3e:71:52:b0 192.168.30.2"]
    port 91075d39-be43-4102-a12d-019f7c40063e
        type: router
        router-port: lrp-91075d39-be43-4102-a12d-019f7c40063e
router 7d415648-8216-4443-ac39-94c462ad7edb (neutron-8d2d2e00-afde-4052-bf30-b9cc93ce4505) (aka router2)
    port lrp-ed598f54-6519-4bed-b30c-483ed67878d2
        mac: "fa:16:3e:6d:3c:eb"
        networks: ["192.168.30.9/24"]
    port lrp-184e0495-03f3-483e-b6fa-b978e9ec8905
        mac: "fa:16:3e:76:6c:62"
        networks: ["192.168.10.1/24"]
router 50641e0d-bcb0-4925-a5ff-8360d178ba47 (neutron-0fd652d1-f17d-464d-9b1c-68fd88dec5c3) (aka router1)
    port lrp-367ac68a-9732-4c91-a458-2fc221491e2f
        mac: "fa:16:3e:f0:55:63"
        networks: ["10.0.0.1/26"]
    port lrp-55edcb76-e904-4dea-8ddb-cb770c3b7aee
        mac: "fa:16:3e:ed:a2:74"
        networks: ["fded:d86e:b73f::1/64"]
    port lrp-59f74080-ff5f-474d-9910-f362122d0ddf
        mac: "fa:16:3e:40:6a:5f"
        networks: ["172.24.4.19/24", "2001:db8::1/64"]
        gateway chassis: [949fe1d5-3db2-49dd-a8b7-7bc7fa119d97]
    port lrp-91075d39-be43-4102-a12d-019f7c40063e
        mac: "fa:16:3e:61:77:68"
        networks: ["192.168.30.1/24"]
    nat a73c165f-ee7a-4dcd-a9b9-fd08ff9380fc
        external ip: "172.24.4.19"
        logical ip: "192.168.30.0/24"
        type: "snat"
    nat e2dd37fe-563c-4849-9f67-ed807610f401
        external ip: "172.24.4.19"
        logical ip: "10.0.0.0/26"
        type: "snat"

[centos@centos networking-ovn]$ openstack router set router2 --route destination=10.0.0.1/26,gateway=192.168.30.1
[centos@centos networking-ovn]$ openstack router set router1 --route destination=192.168.10.0/24,gateway=192.168.30.9

[centos@centos networking-ovn]$ openstack router set router2 --route destination=10.0.0.1/26,gateway=192.168.30.1
[centos@centos networking-ovn]$ openstack router set router1 --route destination=192.168.10.0/24,gateway=192.168.30.9

[centos@centos networking-ovn]$ sudo ip net e ovnmeta-8d552062-879b-477a-b384-69a8961f48a0 ssh cirros@192.168.10.4
cirros@192.168.10.4's password:
$ ping -c1 10.0.0.10
PING 10.0.0.10 (10.0.0.10): 56 data bytes
64 bytes from 10.0.0.10: seq=0 ttl=62 time=1.397 ms

--- 10.0.0.10 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 1.397/1.397/1.397 ms

[centos@centos networking-ovn]$ sudo ip net e ovnmeta-977f0557-159e-493c-86f7-cb28a7b74c1d ssh cirros@10.0.0.10
cirros@10.0.0.10's password:
$ ping -c1 192.168.10.4
PING 192.168.10.4 (192.168.10.4): 56 data bytes
64 bytes from 192.168.10.4: seq=0 ttl=62 time=0.766 ms

--- 192.168.10.4 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.766/0.766/0.766 ms

And through the FIP of VM1, it works as well:

[centos@centos networking-ovn]$ openstack floating ip set --port 51cebfef-39a7-4996-81e6-dd48a4a81dfd 172.24.4.9

[centos@centos networking-ovn]$ ssh cirros@172.24.4.9
The authenticity of host '172.24.4.9 (172.24.4.9)' can't be established.
RSA key fingerprint is SHA256:6LP9nfrF1S3+hO96EVNYdnoT/v3CTKkHAmrGLdmATRk.
RSA key fingerprint is MD5:e8:fd:b8:1e:bf:ad:5b:5c:ac:ce:01:e1:16:97:0e:c3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.24.4.9' (RSA) to the list of known hosts.
cirros@172.24.4.9's password:
$ ping -c1 192.168.10.4
PING 192.168.10.4 (192.168.10.4): 56 data bytes
64 bytes from 192.168.10.4: seq=0 ttl=62 time=1.417 ms

--- 192.168.10.4 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 1.417/1.417/1.417 ms
$