yahoo-eng-team team mailing list archive

[Edward Hope-Morley <1929821@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
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:
  New

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