[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
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/1227506
Title:
Nova fails to boot if there is only one private network and one public
network, while it should implicitly boot from the private one
Status in OpenStack Compute (nova):
Expired
Bug description:
Following the change https://review.openstack.org/#/c/33996/ Nova now
checks if there are multiple networks per tenant and then raises an
error, as it doesn't want to choose arbitrarely.
I understand the need and I don't want to revert this change, but I
think the side-effect where an operator provisions both private and
public networks on the same tenant should be managed.
From my POV, Nova should not raise an error if only those two networks are
found and automatically selects the private one.
That said, if an operator wants to explicitely boot an instance bound to the
public network, he could still do it using the --nic flag.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1227506/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
