yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #76760
[Bug 1811213] Re: Floatingip status changed to error when restart l3-agent
Reviewed: https://review.openstack.org/629960
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4d45699f155a6aa5732c27b572d3288963638ee3
Submitter: Zuul
Branch: master
commit 4d45699f155a6aa5732c27b572d3288963638ee3
Author: LIU Yulong <i@xxxxxxxxxxxx>
Date: Fri Jan 11 09:34:35 2019 +0800
Not set fip to ERROR if it exists on device
The centralized floating IP can exist on the router device
due to some reasons like: uncleaned fip addr, and especially
multiple IP addr adding action: HA router _add_vip() and
Edge router add_ip_address().
This patch catches the IpAddressAlreadyExists error if fip
was already set on the device, and still process next step.
Change-Id: I324f6b96baa0520a0f7ef62a83d81864d7b27999
Closes-Bug: #1811213
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1811213
Title:
Floatingip status changed to error when restart l3-agent
Status in neutron:
Fix Released
Bug description:
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 status of FloatingIP changed to be ERROR
l3-agent.log:
2019-01-08 18:03:25.759 2193 WARNING neutron.agent.l3.dvr_edge_router [-] Unable to configure IP address for centralized floating IP: a5715ce8-e26d-4b1a-8260-8ce82cc86a14: IpAddressAlreadyExists: IP address 172.24.4.31 already configured on qg-2c8abdd4-15.
2019-01-08 18:03:25.760 2193 INFO neutron.agent.l3.router_info [-] Floating ip a5715ce8-e26d-4b1a-8260-8ce82cc86a14 added, status ERROR
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1811213/+subscriptions
References