Fix indexing into subnet list during cluster creation

When creating a cluster using an existing network,
once the network has been selected from the dropdown
the subnet dropdown fails to populate. This is due to
an off-by-one indexing error.

Closes-Bug: #2087843

Change-Id: I0f7b20576e25c9f93ddc90fcfb501422d2adb7e1
This commit is contained in:
Andrew Bonney 2024-11-11 11:49:12 +00:00
parent 3f8a06e895
commit bd7662480f

View File

@ -686,7 +686,7 @@
fixedSubnets = [{value: "", name: fixedSubnetsInitial}];
}
// NOTE(dalees): This hardcoded index could be improved by referencing an object instead.
form[0].tabs[2].items[0].items[0].items[3].titleMap = subnetTitleMap;
form[0].tabs[2].items[0].items[0].items[2].titleMap = subnetTitleMap;
model.fixed_subnet = MODEL_DEFAULTS.fixed_subnet;
}