yahoo-eng-team team mailing list archive

[OpenStack Infra <1776984@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/575562
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5a7c12f245fd665de5a0364059e4ad918def3e12
Submitter: Zuul
Branch:    master

commit 5a7c12f245fd665de5a0364059e4ad918def3e12
Author: Swaminathan Vasudevan <SVasudevan@xxxxxxxx>
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: I78c7ea9f3b6a1cf5b208286eb372da05dc1ba379
    Closes-Bug: #1776984


** 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/1776984

Title:
  DVR: Self recover from the loss of 'fg' ports in FIP Namespace

Status in neutron:
  Fix Released

Bug description:
  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.

  So we need to fix this issue, if this happens, then it should check
  for all the ports within the 'fipnamespace' and recreate the necessary
  plumbing.

  Here is the error log we have been seeing when the 'fg' port was
  missing.

  http://paste.openstack.org/show/723505/

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