yahoo-eng-team team mailing list archive

[Harald Jensås <2040172@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovn_db_sync.OvnSbSynchronizer

When the `sync_hostname_and_physical_networks` method run's it will
compare host physical_networks to mappings in neutrons
`segmenthostmappings` table. Any mappings in neutron that is not seen on
OVN chassis is then treated as "stale" and cleaned up.

This is problematic when there are other plug-ins/agents involved, for
example ML2 networking-baremetal[2]. Any segment-host mapping created
for baremetal nodes are deleted from the database. And since there is
de-duplication[1] on updates from agents - the segment-host mappings are
not re-created unless services are re-started or the baremetal node is
deleted and re-created in the ironic service.

The OvnSbSynchronizer should not remove mappings unless they belong to
OVN hosts.

[1] https://opendev.org/openstack/neutron/commit/176503e610aee16cb5799a77466579bc55129450
[2] https://opendev.org/openstack/networking-baremetal/src/branch/master/networking_baremetal/agent/ironic_neutron_agent.py

** Affects: neutron
     Importance: Undecided
         Status: In Progress

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

Title:
  [OVN] OvnSbSynchronizer - clean/delete segmenthostmappings for
  unrelated hosts

Status in neutron:
  In Progress

Bug description:
  neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovn_db_sync.OvnSbSynchronizer

  When the `sync_hostname_and_physical_networks` method run's it will
  compare host physical_networks to mappings in neutrons
  `segmenthostmappings` table. Any mappings in neutron that is not seen
  on OVN chassis is then treated as "stale" and cleaned up.

  This is problematic when there are other plug-ins/agents involved, for
  example ML2 networking-baremetal[2]. Any segment-host mapping created
  for baremetal nodes are deleted from the database. And since there is
  de-duplication[1] on updates from agents - the segment-host mappings
  are not re-created unless services are re-started or the baremetal
  node is deleted and re-created in the ironic service.

  The OvnSbSynchronizer should not remove mappings unless they belong to
  OVN hosts.

  [1] https://opendev.org/openstack/neutron/commit/176503e610aee16cb5799a77466579bc55129450
  [2] https://opendev.org/openstack/networking-baremetal/src/branch/master/networking_baremetal/agent/ironic_neutron_agent.py

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