yahoo-eng-team team mailing list archive

[Eric Fried <efried@xxxxxxxxxx>]

Public bug reported:

Over the weekend (so since about 3/29) the nova-live-migration job has
been failing 100% with the message:

"Multiple possible networks found, use a Network ID to be more specific"

Example: http://logs.openstack.org/12/648912/1/check/nova-live-
migration/48932a5/job-output.txt.gz#_2019-04-01_08_27_07_901239

Matt identified this as a suspect:

https://review.openstack.org/#/c/601433/

...since it causes us now to create multiple networks. In tempest a
network is always explicitly given, but in the nova-live-migration job
it's not.

** Affects: nova
     Importance: Critical
         Status: Triaged


** Tags: gate-failure

-- 
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/1822605

Title:
  nova-live-migration fails 100% with "Multiple possible networks found,
  use a Network ID to be more specific"

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  Over the weekend (so since about 3/29) the nova-live-migration job has
  been failing 100% with the message:

  "Multiple possible networks found, use a Network ID to be more
  specific"

  Example: http://logs.openstack.org/12/648912/1/check/nova-live-
  migration/48932a5/job-output.txt.gz#_2019-04-01_08_27_07_901239

  Matt identified this as a suspect:

  https://review.openstack.org/#/c/601433/

  ...since it causes us now to create multiple networks. In tempest a
  network is always explicitly given, but in the nova-live-migration job
  it's not.

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