VMs can't be booted with networks without subnet
Bug #1304409 reported by
Sudipta Biswas
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Recently a change in the nova/network/
The following line in the api.py file is causing the issue:
for net in nets:
if not net.get('subnets'):
This has to be fixed to allow users to do boots with networks that do not have a subnet associated with them.
The issue seems to be occuring post the commit done here:
no longer affects: | neutron |
tags: | added: network |
Changed in nova: | |
status: | Invalid → Incomplete |
tags: | added: neutron |
Changed in nova: | |
assignee: | Bence Romsics (bence-romsics) → Geza Gemes (geza-gemes) |
To post a comment you must log in.
Are you saying that an instance should be able to boot without a network? How would you even get into the instance, if you do not have a root password set (which is the case for cloud-init images)? What is the use case for booting an instance without a network?