Bug 1695892 - NetworkType: geneve: Unable to reach an instance via its floating IP
Summary: NetworkType: geneve: Unable to reach an instance via its floating IP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: James Smith
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-03 20:42 UTC by Alexander Chuzhoy
Modified: 2021-03-24 19:22 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-24 19:22:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gerrithub.io 451052 0 None None None 2019-04-16 14:50:55 UTC
Launchpad 1824143 0 None None None 2019-04-10 14:27:29 UTC

Description Alexander Chuzhoy 2019-04-03 20:42:30 UTC
NetworType: geneve: Unable to reach an instances via its floating IP

Environment:
puppet-neutron-14.4.1-0.20190329020333.a6c6114.el8ost.noarch
python3-neutronclient-6.12.0-0.20190312100012.680b417.el8ost.noarch
openvswitch2.11-ovn-common-2.11.0-0.20190129gitd3a10db.el8fdb.x86_64
rhosp-openvswitch-ovn-host-2.11-0.1.el8ost.noarch
puppet-ovn-14.4.1-0.20190325161758.ab61d61.el8ost.noarch
rhosp-openvswitch-ovn-common-2.11-0.1.el8ost.noarch
openvswitch2.11-ovn-host-2.11.0-0.20190129gitd3a10db.el8fdb.x86_64
openstack-tripleo-heat-templates-10.4.1-0.20190329120340.748499d.el8ost.noarch


Steps to reproduce:

1. Deploy OC with either:
parameter_default:
    NeutronBridgeMappings: 'datacentre:br-ex'
    NeutronExternalNetworkBridge: ''
    NeutronNetworkType: geneve
    NeutronNetworkVLANRanges: tenant:1000:2000
    NeutronTunnelTypes: geneve
or
parameter_default:
    NeutronBridgeMappings: ''
    NeutronExternalNetworkBridge: ''
    NeutronNetworkType: geneve
    NeutronNetworkVLANRanges: tenant:1000:2000
    NeutronTunnelTypes: geneve

2.
Launch aninstance in OC and assign it a floating ip. Make sure the to add the necessary openstack security group rules

3. 
Try to reach the instance via ping (or try to reach the undercloud from the instance).


Result:
(overcloud) [stack@undercloud-0 ~]$ openstack server list                                                                                                                                     
+--------------------------------------+--------------+--------+----------------------------------------+--------+---------+
| ID                                   | Name         | Status | Networks                               | Image  | Flavor  |
+--------------------------------------+--------------+--------+----------------------------------------+--------+---------+
| 2254d8ae-f62c-4d14-9500-b821b2022f77 | after_deploy | ACTIVE | tenantgeneve=192.168.32.75, 10.0.0.185 | cirros | m1.tiny |
+--------------------------------------+--------------+--------+----------------------------------------+--------+---------+




(overcloud) [stack@undercloud-0 ~]$ ping -c1 -w1 10.0.0.185
PING 10.0.0.185 (10.0.0.185) 56(84) bytes of data.

--- 10.0.0.185 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


[heat-admin@controller-2 ~]$  ovn-nbctl lr-nat-list neutron-6d8ca565-1ea3-4457-a470-1fc187ee90bc
TYPE             EXTERNAL_IP        LOGICAL_IP            EXTERNAL_MAC         LOGICAL_PORT
dnat_and_snat    10.0.0.185         192.168.32.75         fa:16:3e:18:b5:91    82d76a8a-a086-41f9-a0af-173615b42e6b
snat             10.0.0.198         192.168.32.0/24



[heat-admin@controller-2 ~]$  ovn-nbctl lr-nat-list neutron-6d8ca565-1ea3-4457-a470-1fc187ee90bc                                                                                              
TYPE             EXTERNAL_IP        LOGICAL_IP            EXTERNAL_MAC         LOGICAL_PORT
dnat_and_snat    10.0.0.185         192.168.32.75         fa:16:3e:18:b5:91    82d76a8a-a086-41f9-a0af-173615b42e6b
snat             10.0.0.198         192.168.32.0/24



[heat-admin@controller-2 ~]$ ping -c1 -w1 10.0.0.185
PING 10.0.0.185 (10.0.0.185) 56(84) bytes of data.

--- 10.0.0.185 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms




[heat-admin@controller-2 ~]$ ping -c1 -w1 10.0.0.198
PING 10.0.0.198 (10.0.0.198) 56(84) bytes of data.
64 bytes from 10.0.0.198: icmp_seq=1 ttl=254 time=0.923 ms

--- 10.0.0.198 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.923/0.923/0.923/0.000 ms

Comment 1 Alexander Chuzhoy 2019-04-08 17:24:46 UTC
Tried deployment with both:

NeutronBridgeMappings: 'datacentre:br-ex'
and
NeutronBridgeMappings: ''

Still unable to ping the instance.

Comment 3 Bernard Cafarelli 2019-04-10 14:27:29 UTC
Adding relevant launchpad bug, that tracks a cleanup of OVN THT files to only keep the "HA" versions


Note You need to log in before you can comment on or make changes to this bug.