yahoo-eng-team team mailing list archive

[ibm-cloud-qa <ibm-cloud-qa@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

We have a Juno based openstack cloud build using Packstack. Controller
node, network node and computes nodes each are running on a bare metal
servers with LBaaS agent running on the network node.

- On a tenant,create some LB pools
- Add vip for the pools.
- Associate one of the pool's VIP to a floating IP
- Ping Floating IP of that VIP from outside.
-  While ping is successful to the VIP, disassociate Floating IP from it and check the ping traffic.
- Even after disassociating, ping gets a response.

Stop the ping, wait for a while and then restart the ping. Ping will
fail at this point.


We expect ping to fail as soon as VIP is disassociated with the floating IP.

** Affects: neutron
     Importance: Undecided
         Status: New

** Summary changed:

- VM are reachable from floating IP even after disassociating it from VM port
+ HAProxy VIP are reachable from floating IP even after disassociating it from VIP

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

Title:
  HAProxy VIP are reachable from floating IP even after disassociating
  it from VIP

Status in neutron:
  New

Bug description:
  We have a Juno based openstack cloud build using Packstack. Controller
  node, network node and computes nodes each are running on a bare metal
  servers with LBaaS agent running on the network node.

  - On a tenant,create some LB pools
  - Add vip for the pools.
  - Associate one of the pool's VIP to a floating IP
  - Ping Floating IP of that VIP from outside.
  -  While ping is successful to the VIP, disassociate Floating IP from it and check the ping traffic.
  - Even after disassociating, ping gets a response.

  Stop the ping, wait for a while and then restart the ping. Ping will
  fail at this point.

  
  We expect ping to fail as soon as VIP is disassociated with the floating IP.

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