← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1686449] Re: Fix create instances error when selected network has no subnets

 

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 <wei.ying@xxxxxxxxxxxx>
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


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1686449

Title:
  Fix create instances error when selected network has no subnets

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  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)"

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


References