When we associate a floatingip in an HA router setup, it is properly
associated. However, when we check the status of the Floating ip, it
is shown as empty. The L3 agent ha_router implementation never sets
the status of the floating IP when it's added. This behavior blocks
tempest scenario tests that use FIPs when run against a deployment
with L3 agent HA routers. This fix sets the FIP status to active
when the FIP is added by an HaRouter instance.
Reviewed: https:/ /review. openstack. org/177777 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=30e048d222c 23c8fa07f70fa2d 6a820fa0c88e0c
Committed: https:/
Submitter: Jenkins
Branch: master
commit 30e048d222c23c8 fa07f70fa2d6a82 0fa0c88e0c
Author: sridhargaddam <email address hidden>
Date: Mon Apr 27 14:06:59 2015 +0000
Fix floatingip status for an HA router
When we associate a floatingip in an HA router setup, it is properly
associated. However, when we check the status of the Floating ip, it
is shown as empty. The L3 agent ha_router implementation never sets
the status of the floating IP when it's added. This behavior blocks
tempest scenario tests that use FIPs when run against a deployment
with L3 agent HA routers. This fix sets the FIP status to active
when the FIP is added by an HaRouter instance.
Co-Authored-By: Assaf Muller <email address hidden> 483a927ce9fed30 777e84df96a
Closes-Bug: #1449049
Change-Id: I7a3de36b64132e