yahoo-eng-team team mailing list archive

[Lucas Alvares Gomes <1883559@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In OVN, if we change the value of the
[ovn]/enable_distributed_floating_ip configuration option and restart
the service, the OVN driver will not reflect this change in the existing
NAT entries.

Say you have a enable_distributed_floating_ip as True and then you
change it to False, new NAT entries (floating ips) will have the
"external_mac" column empty when they are created but, pre-existing NAT
entries won't be updated and will have their "external_mac" set.
Requiring someone to manually update the OVN database to clear out that
field.

** Affects: neutron
     Importance: Medium
     Assignee: Lucas Alvares Gomes (lucasagomes)
         Status: In Progress

** Changed in: neutron
       Status: New => Confirmed

** Changed in: neutron
   Importance: Undecided => Medium

** Changed in: neutron
     Assignee: (unassigned) => Lucas Alvares Gomes (lucasagomes)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1883559

Title:
  [OVN] enable_distributed_floating_ip changes are not applied for
  existing NAT entries

Status in neutron:
  In Progress

Bug description:
  In OVN, if we change the value of the
  [ovn]/enable_distributed_floating_ip configuration option and restart
  the service, the OVN driver will not reflect this change in the
  existing NAT entries.

  Say you have a enable_distributed_floating_ip as True and then you
  change it to False, new NAT entries (floating ips) will have the
  "external_mac" column empty when they are created but, pre-existing
  NAT entries won't be updated and will have their "external_mac" set.
  Requiring someone to manually update the OVN database to clear out
  that field.

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