← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1637118] [NEW] Nova erroneously asserts a subnet is required on a network to boot an instance

 

Public bug reported:

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-5c4a-4700-a333-e5a39be51beb
    +---------------------------+--------------------------------------+
    | Field                     | Value                                |
    +---------------------------+--------------------------------------+
    | admin_state_up            | UP                                   |
    | availability_zone_hints   |                                      |
    | availability_zones        | nova                                 |
    | created_at                | 2016-10-12T23:32:35Z                 |
    | description               |                                      |
    | id                        | facb7425-5c4a-4700-a333-e5a39be51beb |
    | ipv4_address_scope        | None                                 |
    | ipv6_address_scope        | None                                 |
    | mtu                       | 1450                                 |
    | name                      | lb-mgmt-net                          |
    | port_security_enabled     | True                                 |
    | project_id                | 2da3ff5836314dadb6bee8151cb649c8     |
    | project_id                | 2da3ff5836314dadb6bee8151cb649c8     |
    | provider:network_type     | vxlan                                |
    | provider:physical_network | None                                 |
    | provider:segmentation_id  | 72                                   |
    | revision_number           | 6                                    |
    | router:external           | Internal                             |
    | shared                    | False                                |
    | status                    | ACTIVE                               |
    | subnets                   |                                      |
    | tags                      | []                                   |
    | updated_at                | 2016-10-26T15:32:06Z                 |
    +---------------------------+--------------------------------------+
    $ openstack server create test --image cirros-0.3.4-x86_64-uec --flavor m1.tiny  --nic net-id=facb7425-5c4a-4700-a333-e5a39be51beb
    Network facb7425-5c4a-4700-a333-e5a39be51beb requires a subnet in order to boot instances on. (HTTP 400) (Request-ID: req-11ce6a29-d1a7-48ab-85a0-8fea1e28da53)

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1637118

Title:
  Nova erroneously asserts a subnet is required on a network to boot an
  instance

Status in OpenStack Compute (nova):
  New

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-5c4a-4700-a333-e5a39be51beb
      +---------------------------+--------------------------------------+
      | Field                     | Value                                |
      +---------------------------+--------------------------------------+
      | admin_state_up            | UP                                   |
      | availability_zone_hints   |                                      |
      | availability_zones        | nova                                 |
      | created_at                | 2016-10-12T23:32:35Z                 |
      | description               |                                      |
      | id                        | facb7425-5c4a-4700-a333-e5a39be51beb |
      | ipv4_address_scope        | None                                 |
      | ipv6_address_scope        | None                                 |
      | mtu                       | 1450                                 |
      | name                      | lb-mgmt-net                          |
      | port_security_enabled     | True                                 |
      | project_id                | 2da3ff5836314dadb6bee8151cb649c8     |
      | project_id                | 2da3ff5836314dadb6bee8151cb649c8     |
      | provider:network_type     | vxlan                                |
      | provider:physical_network | None                                 |
      | provider:segmentation_id  | 72                                   |
      | revision_number           | 6                                    |
      | router:external           | Internal                             |
      | shared                    | False                                |
      | status                    | ACTIVE                               |
      | subnets                   |                                      |
      | tags                      | []                                   |
      | updated_at                | 2016-10-26T15:32:06Z                 |
      +---------------------------+--------------------------------------+
      $ openstack server create test --image cirros-0.3.4-x86_64-uec --flavor m1.tiny  --nic net-id=facb7425-5c4a-4700-a333-e5a39be51beb
      Network facb7425-5c4a-4700-a333-e5a39be51beb requires a subnet in order to boot instances on. (HTTP 400) (Request-ID: req-11ce6a29-d1a7-48ab-85a0-8fea1e28da53)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1637118/+subscriptions