On 5/30/2018 9:41 AM, Matt Riedemann wrote:
Thanks for your patience in debugging this Massimo! I'll get a bug
reported and patch posted to fix it.
I'm tracking the problem with this bug:
https://bugs.launchpad.net/nova/+bug/1774205
I found that this has actually been fixed since Pike:
On 5/30/2018 5:21 AM, Massimo Sgaravatto wrote:
The problem is indeed with the tenant_id
When I create a VM, tenant_id is ee1865a76440481cbcff08544c7d580a
(SgaraPrj1), as expected
But when, as admin, I run the "nova migrate" command to migrate the very
same instance, the tenant_id is
On 5/29/2018 8:23 PM, Chris Apsey wrote:
I want to echo the effectiveness of this change - we had vif failures
when launching more than 50 or so cirros instances simultaneously, but
moving to daemon mode made this issue disappear and we've tested 5x that
amount. This has been the single
The problem is indeed with the tenant_id
When I create a VM, tenant_id is ee1865a76440481cbcff08544c7d580a
(SgaraPrj1), as expected
But when, as admin, I run the "nova migrate" command to migrate the very
same instance, the tenant_id is 56c3f5c047e74a78a71438c4412e6e13 (admin) !
Cheers, Massimo
Hi,
just to let you know. Problem is now gone. Instances boot up with working
network interface.
Thanks a lot,
Radu
On Tue, 2018-05-29 at 21:23 -0400, Chris Apsey wrote:
I want to echo the effectiveness of this change - we had vif failures when
launching more than 50 or so cirros instances
