Bug 1459181 - [BACKPORT] [Neutron] Don't add duplicate metadata rules after router update
Summary: [BACKPORT] [Neutron] Don't add duplicate metadata rules after router update
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 10.0 (Newton)
Hardware: All
OS: Linux
medium
medium
Target Milestone: z4
: 10.0 (Newton)
Assignee: Brian Haley
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-06 13:21 UTC by Masaki Furuta ( RH )
Modified: 2020-12-14 08:49 UTC (History)
9 users (show)

Fixed In Version: openstack-neutron-9.4.0-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-06 17:17:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 473478 0 None MERGED Don't add duplicate metadata rules after router update 2020-03-20 20:55:00 UTC
Red Hat Product Errata RHBA-2017:2663 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2017-09-06 20:58:42 UTC

Description Masaki Furuta ( RH ) 2017-06-06 13:21:47 UTC
Description of problem:
  
- Customer/We still see "Duplicate iptables rule detected" warning messages in l3-agent.log file on OSP10/Newton with 142b68f0 .

- To eliminate it, please introduce upstream fix on https://bugs.launchpad.net/neutron/+bug/1658460 

~~~
commit 1257a3f203aacfbbe16c1afa79893b8b990a1a57
Author: Quan Tian <tianquan>
Date:   Sun Jan 22 16:49:24 2017 +0800

    Don't add duplicate metadata rules after router update
    
    For a HA router, when it's updated, the l3 agents which are standby
    always call the after_router_added method, then duplicate metadata
    rules are added to iptables table. Althrough these rules will not be
    applied to system because of the _weed_out_duplicates method, they will
    grow linearly with router update operations.
    
    Because these metadata rules are added once router is added to the agent
    and will not be cleaned until router is removed, calling the add_rule
    method in after_router_updated is a waste.
    
    This patch removes adding metadata rules in after_router_updated.
    
    Change-Id: I6650f1071499ed6cabd936bb0fb36b32a4b60bca
    Closes-Bug: #1658460
~~~


Version-Release number of selected component (if applicable):
  Red Hat OpenStack Platform 10

How reproducible:
  Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Brian Haley 2017-06-12 15:29:16 UTC
https://review.openstack.org/#/c/473478/ created.  Once that merges I'll cherry-pick back to 10.0

Comment 4 errata-xmlrpc 2017-09-06 17:17:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2663


Note You need to log in before you can comment on or make changes to this bug.