Subnet selection box fails to populate when creating a cluster with an existing network

Bug #2087843 reported by Andrew Bonney
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum UI
New
Undecided
Unassigned

Bug Description

It appears there is an off by one error in https://github.com/openstack/magnum-ui/blob/master/magnum_ui/static/dashboard/container-infra/clusters/workflow/workflow.service.js#L689. When creating a cluster and disabling network creation, the Networks list correctly populates. When you select a network from the list, this creates an error in the JS console and the Subnet selection list fails to populate.

Replacing items[3] with items[2] fixes this indexing error and allows the Subnet list to populate. As the comment suggests, it might ideally be nice to have a less brittle approach to this, but the basic fix is at least simple.

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.