yahoo-eng-team team mailing list archive

[OpenStack Infra <1929821@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/794604
Committed: https://opendev.org/openstack/neutron/commit/a03c240ef4ea1d4b874b618dbd0163a3a2f7024c
Submitter: "Zuul (22348)"
Branch:    master

commit a03c240ef4ea1d4b874b618dbd0163a3a2f7024c
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Thu Jun 3 14:49:45 2021 +0000

    Populate self.floating_ips_dict using "ip rule" information
    
    When the L3 agent starts, reads the floating IP rule priority from
    a state file created by "FipRulePriorityAllocator". In case of not
    having all floating IPs registers in this file, the method:
    - Creates a new priority for this floating IP.
    - Creates the "ip rule" in the namespace.
    - Adds a new entry in "self.floating_ips_dict".
    
    All "ip rules" present in the namespace that do not match the
    registered fixed IP address ("from") and the priority assigned
    are deleted.
    
    Closes-Bug: #1891673
    Closes-Bug: #1929821
    
    Change-Id: Ia3fbde3304ab5f3c309dc62dbf58274afbcf4614


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

Title:
  [dvr] misleading fip rule priority not found error message

Status in neutron:
  Fix Released

Bug description:
  The fix for bug 1891673 added an error log like "Rule priority not
  found for floating ip a.b.c.d" such that if the ip rule priority
  information needed to configure a floating ip could not be found (in
  the fip-priorities file) the error message is logged. This error
  message can be misleading since not all floating ips will have or need
  a priority allocation since only those configured in qrouter
  namespaces need them but not fips for unbound ports that are
  configured in the snat ns (dvr). We should gate retrieving that
  information on whether the fixed_ip associated with fip is bound or
  not to avoid having this misleading error messages.

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