yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1999582@xxxxxxxxxxxxxxxxxx>]

Hello do3meli:

This configuration parameter "live_migration_wait_for_vif_plug" belongs
to Nova. If you check the documentation, that parameter will tell Nova
if it needs to wait (and how long) or not for the "vif-plugged-event",
sent by Neutron.

When using ML2/OVS, if the port admin status is set to down, the agent
reports it as DOWN and the Neutron server doesn´t send the expected
"vif-plugged-event".

This is not a Neutron bug but something that should be documented in the
Nova documentation.

Regards.


** Changed in: neutron
       Status: New => 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/1999582

Title:
  vm live migration not working when port is admin down

Status in neutron:
  Invalid

Bug description:
  having a vm with a provider network port that has it's status set to
  "admin down" won't let this vm migrate successfully. the source
  compute host will abort the migration with the following message:

  Timed out waiting for events: [('network-vif-plugged',
  '8066f303-a72c-4784-9fc0-de5f7d8a993f'), ('network-vif-plugged',
  '6c167efe-3a55-46d1-baf1-4962b3bc387f')]. If these timeouts are a
  persistent issue it could mean the networking backend on host
  computeXXX does not support sending these events unless there are port
  binding host changes which does not happen at this point in the live
  migration process. You may need to disable the
  live_migration_wait_for_vif_plug option on host computeXXX.:
  eventlet.timeout.Timeout: 300 seconds

  setting the port admin status up and re-running the life migration let
  the vm successfully complete. Therefore the logic for the
  live_migration_wait_for_vif_plug settings should be adjusted to take
  into consideration if a port should be up or not.

  Environment:

  - Ubuntu 20.04.5 with Cloud Archive Repositories in version 19.4.0-0ubuntu1~cloud0 on Xena branch
  - Using ML2 with OVS on physical provider network

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