Fix create instances error when selected network has no subnets

[wei.ying]

Env: devstack master branch

Desc:

When a project is only one available network, and the network without subnets, the network should not be used to create instances.

If use this network api will return:

"Network f1a03328-60d0-4b0e-a4a0-d25ec0d185c4 requires a subnet in order to boot instances on. (HTTP 400) (Request-ID: req-e8a03012-6f03-4797-aaf0-0dfa9b434746)"

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/460221
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a92d1658d8b3d824fa38ed32dbbee100b0ca77de
Submitter: Zuul
Branch: master

commit a92d1658d8b3d824fa38ed32dbbee100b0ca77de
Author: wei.ying <email address hidden>
Date: Thu Apr 27 00:39:35 2017 +0800

    Fix the network subnets check in create instance form

    If a project is only one available network, we need to verify
    whether it contains subnets, otherwise nova api will return
    "Network f1a03328-60d0-4b0e-a4a0-d25ec0d185c4 requires
    a subnet in order to boot instances on. (HTTP 400)"

    The default network may not contain subnets[1]. We should first
    query the networks that contains the subnets, and then get the
    default network from the networks.

    [1] https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/launch-instance-model.service.js#L478-#L484

    Change-Id: I16f7f8cddf045445ed026f62366957de9d289c03
    Closes-Bug: #1686449

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/horizon 13.0.0.0b3 development milestone.