yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77793
[Bug 1822605] Re: nova-live-migration fails 100% with "Multiple possible networks found, use a Network ID to be more specific"
Reviewed: https://review.openstack.org/649036
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bed9d49163a70e063835d49aff3757f2c1a798f3
Submitter: Zuul
Branch: master
commit bed9d49163a70e063835d49aff3757f2c1a798f3
Author: Matt Riedemann <mriedem.os@xxxxxxxxx>
Date: Mon Apr 1 09:58:01 2019 -0400
Pass --nic when creating servers in evacuate integration test script
Devstack change Ib2e7096175c991acf35de04e840ac188752d3c17 started
creating a second network which is shared when tempest is enabled.
This causes the "openstack server create" and "nova boot" commands
in test_evacuate.sh to fail with:
Multiple possible networks found, use a Network ID to be more specific.
This change selects the non-shared network and uses it to create
the servers during evacuate testing.
Change-Id: I2085a306e4d6565df4a641efabd009a3bc182e87
Closes-Bug: #1822605
** Changed in: nova
Status: In Progress => Fix Released
--
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):
Fix Released
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
References