make security group optional in new launch instance

Bug #1501722 reported by Masco on 2015-10-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Low
Masco

Bug Description

security group available list is mess in new launch instance form.

according to API doc and legacy launch instance form security group is optional.
so in new launch instance form also it should be optional but it is not.

Masco (masco) on 2015-10-01
Changed in horizon:
assignee: nobody → Masco Kaliyamoorthy (masco)

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

Changed in horizon:
status: New → In Progress
Changed in horizon:
importance: Undecided → Low

Reviewed: https://review.openstack.org/229835
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=dedc10f6843320c129d9196fdb8821c36cf75502
Submitter: Jenkins
Branch: master

commit dedc10f6843320c129d9196fdb8821c36cf75502
Author: Masco Kaliyamoorthy <email address hidden>
Date: Thu Oct 1 17:03:27 2015 +0530

    security group not mandatory to create instance

    as per the nova api and legacy launch instance,
    the security group is not mandatory option to create an instance.

    but in the new launch instance form, it is marked as
    mandatory and it is not allowed to create/launch
    an instance if no security group was selected.

    this patch making the security group is optional.

    Change-Id: Ib381a16922abaf2e704c6a46a8189aec23adfbaa
    Closes-Bug: #1501722

Changed in horizon:
status: In Progress → Fix Committed
Changed in horizon:
milestone: none → mitaka-2

This issue was fixed in the openstack/horizon 9.0.0.0b2 development milestone.

Changed in horizon:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers