Launch Instance NG does not auto select default security group or default to selecting the only network in a Project

Bug #1580357 reported by Peter Nordquist
This bug report is a duplicate of:  Bug #1587681: new launch instance wizard defaults. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
New
Undecided
Unassigned

Bug Description

In the Mitaka Release of Horizon, the Launch Instance NG panels do not select the 'default' security group and if there is only one network in a Project it does not default to that network. In the Launch Instance Legacy workflow, this defaulted to the 'default' security group and if you only had one network it defaulted to select that network. In Mitaka, the Launch Instance Legacy workflow no longer selects the 'default' security group since it is defaulting to using the string instead of the id of the 'default' network and this change broke that [0]. I'm not expecting the Launch Instance Legacy workflow to be fixed, just documenting that fact since I switched back to that workflow expecting it to work like the Kilo dashboard.

[0]: https://github.com/openstack/horizon/commit/5562694

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.