VMs can't be booted with networks without subnet

[Sudipta Biswas]

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

[Thang Pham (thang-pham)]

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?

[hzxiongwenwu (xwwzzy)]

it no sense to boot a instance without a network.

[Sudipta Biswas (sbiswas7)]

I referred to networks that do not have a subnet associated with them.
I did not mean booting an instance without a network.

[Brent Eagles (beagles)]

Actually this seems like a duplicate (or at least a close relative) of 1252410. There are other BZs related to this topic as well:

https://bugs.launchpad.net/nova/+bug/1039665
https://bugs.launchpad.net/nova/+bug/1175464

In short, this functionality is meant to be dependent on a neutron extension. Will the reporter review the aforementioned BZs and the referenced patch with this information and possible refine this BZ if necessary?

On a related note, did this work for you with neutron before? If so, can you specify the release?

[Sudipta Biswas (sbiswas7)]

This did work in the past when we were at Havana and worked in Ice House - just few weeks before it released.
The problem is possibly fixed with: https://bugs.launchpad.net/nova/+bug/1175464 (https://review.openstack.org/#/c/59578/)
But that change is not merged yet.

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/200046

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/284095

[OpenStack Infra (hudson-openstack)]

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/200046
Reason: This patch has been idle for a long time, so I am abandoning it to keep the review clean sane. If you're interested in still working on this patch, then please unabandon it and upload a new patchset.

[Markus Zoeller (markus_z) (mzoeller)]

Cleanup
=======

There are no open reviews for this bug report since more than 2 weeks.
To signal that to other contributors which might provide patches for
this bug, I switch the status from "In Progress" to "Confirmed" and
remove the assignee.
Feel free to add yourself as assignee and to push a review for it.

[Markus Zoeller (markus_z) (mzoeller)]

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