yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  VMs can't be booted with networks without subnet

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Recently a change in the nova/network/neutronv2/api.py file is causing
  nova boots to fail for networks that do not have a subnet associated
  with them.

  The following line in the api.py file is causing the issue:

              for net in nets:
                  if not net.get('subnets'):
                      raise exception.NetworkRequiresSubnet(
                          network_uuid=net['id'])

  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:

  https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commitdiff;h=45e2398f0c01c327db46ce92fb9dda886455db9d

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