DVR: Restarting l3 agent loses centralized fip ip on qg-interface
When l3 agent is restarted on a dvr_snat node that is configured
for L3_HA and has a centralized FloatingIP configured to the
qg-interface in the snat_namespace, that FloatingIP is not
re-configured to the qg-interface when agent starts.
The reason being, the cidr is not being retrieved from the
keepalived instance and only retrieved from the
centralized_fip_cidr_set.
If 'L3_HA' is configured we need to retrieve it from the keepalived
instance.
This patch fixes the problem by retrieving the cidrs from the
keepalived instance for the qg-interface.
Reviewed: https:/ /review. openstack. org/555952 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=64028a389ff 904f15e471b44bd 5b3979c5db2cd2
Committed: https:/
Submitter: Zuul
Branch: master
commit 64028a389ff904f 15e471b44bd5b39 79c5db2cd2
Author: Swaminathan Vasudevan <email address hidden>
Date: Fri Mar 23 15:11:13 2018 -0700
DVR: Restarting l3 agent loses centralized fip ip on qg-interface
When l3 agent is restarted on a dvr_snat node that is configured
for L3_HA and has a centralized FloatingIP configured to the
qg-interface in the snat_namespace, that FloatingIP is not
re-configured to the qg-interface when agent starts.
The reason being, the cidr is not being retrieved from the _fip_cidr_ set.
keepalived instance and only retrieved from the
centralized
If 'L3_HA' is configured we need to retrieve it from the keepalived
instance.
This patch fixes the problem by retrieving the cidrs from the
keepalived instance for the qg-interface.
Change-Id: I848a20d06e2d34 4503a4cb1776dbe 2617d91bc41
Closes-Bug: #1740450