Nova erroneously asserts a subnet is required on a network to boot an instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Deploying an instance attached to a network with a subnet is infact valid, since that instance could communicate via IPv6 link-local addresses or non-IP protocols. Obviously nova metadata wouldn't work, but the instance could otherwise be used. Nova should not assert that a network must have a subnet.
$ openstack network show facb7425-
+--
| Field | Value |
+--
| admin_state_up | UP |
| availability_
| availability_zones | nova |
| created_at | 2016-10-
| description | |
| id | facb7425-
| ipv4_address_scope | None |
| ipv6_address_scope | None |
| mtu | 1450 |
| name | lb-mgmt-net |
| port_security_
| project_id | 2da3ff5836314da
| project_id | 2da3ff5836314da
| provider:
| provider:
| provider:
| revision_number | 6 |
| router:external | Internal |
| shared | False |
| status | ACTIVE |
| subnets | |
| tags | [] |
| updated_at | 2016-10-
+--
$ openstack server create test --image cirros-
Network facb7425-
tags: | added: neutron |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: ipv6 |
Looking through Nova code it looks like this validation was introduced to fix a previous Nova bug https:/ /bugs.launchpad .net/nova/ +bug/1252410.