yahoo-eng-team team mailing list archive

[Brian Haley <1800141@xxxxxxxxxxxxxxxxxx>]

Had to move this back from neutron to flip the status bit.

** Project changed: python-openstackclient => neutron

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1800141

Title:
  Floating IP disassociation does not work

Status in neutron:
  Invalid

Bug description:
  Removing a FIP from a port does not work:

  
  [centos@centos networking-ovn]$ openstack floating ip set --port 51cebfef-39a7-4996-81e6-dd48a4a81dfd 003a724b-24ca-4e6c-a9eb-1d0b58221300

  
  [centos@centos networking-ovn]$ sudo ovn-nbctl list nat |grep dnat_and_snat -B5
  external_ids        : {"neutron:fip_id"="003a724b-24ca-4e6c-a9eb-1d0b58221300", "neutron:fip_port_id"="51cebfef-39a7-4996-81e6-dd48a4a81dfd", "neutron:revision_number"="2", "neutron:router_name"="neutron-0fd652d1-f17d-464d-9b1c-68fd88dec5c3"}
  external_ip         : "172.24.4.24"
  external_mac        : []
  logical_ip          : "10.0.0.10"
  logical_port        : []
  type                : dnat_and_snat

  [centos@centos networking-ovn]$ openstack floating ip unset 172.24.4.24
  [centos@centos networking-ovn]$ ping 172.24.4.24
  PING 172.24.4.24 (172.24.4.24) 56(84) bytes of data.
  64 bytes from 172.24.4.24: icmp_seq=1 ttl=63 time=0.925 ms
  64 bytes from 172.24.4.24: icmp_seq=2 ttl=63 time=0.385 ms
  ^C
  --- 172.24.4.24 ping statistics ---
  2 packets transmitted, 2 received, 0% packet loss, time 1000ms
  rtt min/avg/max/mdev = 0.385/0.655/0.925/0.270 ms


  [centos@centos networking-ovn]$ sudo ovn-nbctl list nat |grep dnat_and_snat -B5
  external_ids        : {"neutron:fip_id"="003a724b-24ca-4e6c-a9eb-1d0b58221300", "neutron:fip_port_id"="51cebfef-39a7-4996-81e6-dd48a4a81dfd", "neutron:revision_number"="2", "neutron:router_name"="neutron-0fd652d1-f17d-464d-9b1c-68fd88dec5c3"}
  external_ip         : "172.24.4.24"
  external_mac        : []
  logical_ip          : "10.0.0.10"
  logical_port        : []
  type                : dnat_and_snat

  If I try to unset the FIP it still "succeeds" from an API perspective:

  [centos@centos networking-ovn]$ openstack floating ip unset 172.24.4.24ç
  [centos@centos networking-ovn]$ ping 172.24.4.24
  PING 172.24.4.24 (172.24.4.24) 56(84) bytes of data.
  64 bytes from 172.24.4.24: icmp_seq=1 ttl=63 time=0.925 ms
  64 bytes from 172.24.4.24: icmp_seq=2 ttl=63 time=0.385 ms
  ^C
  --- 172.24.4.24 ping statistics ---
  2 packets transmitted, 2 received, 0% packet loss, time 1000ms
  rtt min/avg/max/mdev = 0.385/0.655/0.925/0.270 ms

  [centos@centos networking-ovn]$ sudo ovn-nbctl list nat |grep dnat_and_snat -B5
  external_ids        : {"neutron:fip_id"="003a724b-24ca-4e6c-a9eb-1d0b58221300", "neutron:fip_port_id"="51cebfef-39a7-4996-81e6-dd48a4a81dfd", "neutron:revision_number"="2", "neutron:router_name"="neutron-0fd652d1-f17d-464d-9b1c-68fd88dec5c3"}
  external_ip         : "172.24.4.24"
  external_mac        : []
  logical_ip          : "10.0.0.10"
  logical_port        : []
  type                : dnat_and_snat

  
  Looks like   DeleteNATRuleInLRouterCommand is not taking effect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1800141/+subscriptions