yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

Ever since this change in Newton:
https://review.openstack.org/#/c/275073/

Nova will set the 'migrating_to' field in the port's binding:profile
dict for live migration to fix an issue with L3 connectivity with DVR
(see the details in bug 1456073).

The problem is the code that sets that up in nova here:

https://github.com/openstack/nova/blob/75d52556066cf56b33e61bc4a80b6dc81b846c07/nova/network/neutronv2/api.py#L433

Is called from non-live-migration operations:

evacuate:
https://github.com/openstack/nova/blob/75d52556066cf56b33e61bc4a80b6dc81b846c07/nova/compute/manager.py#L3206

resize:
https://github.com/openstack/nova/blob/75d52556066cf56b33e61bc4a80b6dc81b846c07/nova/compute/manager.py#L4497

This does not seem to be an issue with neutron even though there is code
in neutron that keys off this field to determine if a live migration is
being performed:

https://github.com/openstack/neutron/blob/a388701ddfe628e9a5bd16a78422164799b11ef8/neutron/plugins/ml2/drivers/macvtap/mech_driver/mech_macvtap.py#L69

At worst it's a functional bug which can cause issues with migrating
servers using DVR and some types of networking backends. At least it's
unnecessary nova<>neutron API traffic during non-live migration move
operations.

** Affects: nova
     Importance: Low
         Status: Triaged


** Tags: evacuate neutron resize

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1814837

Title:
  port binding:profile migrating_to should only be set during live
  migration

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  Ever since this change in Newton:
  https://review.openstack.org/#/c/275073/

  Nova will set the 'migrating_to' field in the port's binding:profile
  dict for live migration to fix an issue with L3 connectivity with DVR
  (see the details in bug 1456073).

  The problem is the code that sets that up in nova here:

  https://github.com/openstack/nova/blob/75d52556066cf56b33e61bc4a80b6dc81b846c07/nova/network/neutronv2/api.py#L433

  Is called from non-live-migration operations:

  evacuate:
  https://github.com/openstack/nova/blob/75d52556066cf56b33e61bc4a80b6dc81b846c07/nova/compute/manager.py#L3206

  resize:
  https://github.com/openstack/nova/blob/75d52556066cf56b33e61bc4a80b6dc81b846c07/nova/compute/manager.py#L4497

  This does not seem to be an issue with neutron even though there is
  code in neutron that keys off this field to determine if a live
  migration is being performed:

  https://github.com/openstack/neutron/blob/a388701ddfe628e9a5bd16a78422164799b11ef8/neutron/plugins/ml2/drivers/macvtap/mech_driver/mech_macvtap.py#L69

  At worst it's a functional bug which can cause issues with migrating
  servers using DVR and some types of networking backends. At least it's
  unnecessary nova<>neutron API traffic during non-live migration move
  operations.

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