yahoo-eng-team team mailing list archive

[Nate Johnston <1899037@xxxxxxxxxxxxxxxxxx>]

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

** Changed in: neutron
       Status: In Progress => Invalid

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

Title:
  ML2OVN migration script does not set proper bridge mappings

Status in neutron:
  Invalid

Bug description:
  ML2OVS -> ML2OVN migration on non-DVR environment (3 controllers + 2 computes) is failing with default (empty) bridge mapping settings on compute nodes.
  File /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovn-ha.yaml contains the following:
    ComputeParameters:
      NeutronBridgeMappings: ""

  This causes that after the overcloud update that is performed during
  the migration procedure all existing VMs are not accessible.

  Workaround is to set in /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovn-ha.yaml 
    ComputeParameters:
      NeutronBridgeMappings: "tenant:br-isolated"
  before staring the migration.

  The issue does not happen when DVR is enabled.

  In case of SR-IOV or any other no-DVR case when compute nodes are
  connected to the external network and need to be able to launch VM
  instances on the external network we need to specify full value of
  configured bridge mappings (not only tenant) before staring the
  migration.

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