DVR: Self recover from the loss of 'fg' ports in FIP Namespace
Sometimes we have seen the 'fg' ports within the fip-namespace
either goes down, not created in time or getting deleted due to
some race conditions.
When this happens, the code tries to recover itself after couple
of exceptions when there is a router_update message.
But after recovery we could see that the fip-namespace is
recreated and the 'fg-' port is plugged in and active, but the
'fpr' and the 'rfp' ports are missing which leads to the
FloatingIP failure.
This patch will fix this issue by checking for the missing devices
in all router_updates.
Change-Id: I78c7ea9f3b6a1cf5b208286eb372da05dc1ba379
Closes-Bug: #1776984
(cherry picked from commit 5a7c12f245fd665de5a0364059e4ad918def3e12)
Reviewed: https:/ /review. openstack. org/578494 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=e5f292aa8a4 388d4cf0f70692d 85d830704511fc
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit e5f292aa8a4388d 4cf0f70692d85d8 30704511fc
Author: Swaminathan Vasudevan <email address hidden>
Date: Thu Jun 14 13:49:23 2018 -0700
DVR: Self recover from the loss of 'fg' ports in FIP Namespace
Sometimes we have seen the 'fg' ports within the fip-namespace
either goes down, not created in time or getting deleted due to
some race conditions.
When this happens, the code tries to recover itself after couple
of exceptions when there is a router_update message.
But after recovery we could see that the fip-namespace is
recreated and the 'fg-' port is plugged in and active, but the
'fpr' and the 'rfp' ports are missing which leads to the
FloatingIP failure.
This patch will fix this issue by checking for the missing devices
in all router_updates.
Change-Id: I78c7ea9f3b6a1c f5b208286eb372d a05dc1ba379 de5a0364059e4ad 918def3e12)
Closes-Bug: #1776984
(cherry picked from commit 5a7c12f245fd665