Nova fails to boot if there is only one private network and one public network, while it should implicitly boot from the private one

Bug #1227506 reported by Sylvain Bauza on 2013-09-19
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Medium
Unassigned

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.

tags: added: network
Changed in nova:
assignee: nobody → Sylvain Bauza (sylvain-bauza)
Mathew Odden (locke105) on 2013-10-05
summary: Nova fails to boot if there is only one private network and one public
- network, while it should implicetly boot from the private one
+ network, while it should implicitly boot from the private one
Changed in nova:
status: New → Confirmed

Fix proposed to branch: master
Review: https://review.openstack.org/72384

Changed in nova:
status: Confirmed → In Progress
Sean Dague (sdague) on 2014-09-09
Changed in nova:
assignee: Sylvain Bauza (sylvain-bauza) → nobody
status: In Progress → Confirmed
importance: Undecided → Medium
Changed in nova:
assignee: nobody → tcs_openstack_group (tcs-openstack-group)
Changed in nova:
assignee: tcs_openstack_group (tcs-openstack-group) → Kanchan Gupta (kanchan-gupta1)
Changed in nova:
status: Confirmed → In Progress
Changed in nova:
status: In Progress → Confirmed
Justin Shepherd (jshepher) wrote :

Have not seen this bug on kilo. Is this still an issue?

Changed in nova:
assignee: Kanchan Gupta (kanchan-gupta1) → nobody
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers