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
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Medium
|
Unassigned |
Bug Description
Following the change https:/
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) |
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 |
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 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/72384
Review: https:/