Description of problem: Associating a Floating IP to and instance then disassociating the Floating IP - connectivity to an external IP fails. Version-Release number of selected component (if applicable): opendaylight-8.0.0-5.el7ost.noarch How reproducible: It doesn't happen all the time. It may be related to the locations of the NAPT switch and the instance. Steps to Reproduce: 1. Launch an instance and associate it with a FIP 2. Connect to the instance via console or from another instance 3. Check connectivity to an external IP (that is not part of Neutron) 4. Disassociate the FIP from the instance 5. Check connectivity to an external IP (that is not part of Neutron) 6. Verify that there is no connectivity Actual results: Expected results: Additional info:
I tried the same use-case in a multi-node setup where NAPT switch is scheduled on a different Compute node and not on the Compute node where the VM is spawned, but could not reproduce the issue. Tried multiple times but the use-case seems to work fine. @Itzik, please attach logs to this BZ and if possible try to provide me access to the setup when the issue is seen - I can take a close look at it.
The removal of FIP was causing the external learned ip's to be removed. This solved by https://git.opendaylight.org/gerrit/#/c/69777/
On bare metal it doesn't work with 8.0.0-11
To be clear it's bare metal with VLAN setup.
Some updates: ------------- This issue is seen only with VLAN tenant networks and NOT with VxLAN tenant networks. +---------------------------+ | 8.8.8.8 (External Server) | +-----------+---------------+ | +------+-------------+----------------------+ | External Network (FLAT/VLAN) | | ---+-------------------------------+-------+ | | Tenant VLAN Network | | | | | | | +-+------+---------+ +-----------+---------+ | | | ComputeNode | | NAPT Switch | | hosting VM | | | | (10.0.0.8) | +------------------+ +---------------------+ So, in a VLAN tenant network when the issue was reproduced, the problem was a missing Table-21 entry after DNAT (sample flow *) for the return traffic from 8.8.8.8 to VM. I had a look at the config datastore and there was no flow in the config store as well. [*] table=21, priority=42,ip,metadata=0x30d46/0xfffffe,nw_dst=10.0.0.8 actions=set_field:fa:16:3e:62:20:80->eth_dst,load:0x700->NXM_NX_REG6[],resubmit(,220)
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/RHEA-2018:2086