no option to override the fixed_subnet when creating a new cluster
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Magnum UI |
In Progress
|
Undecided
|
Felipe Reyes | |||
| Ubuntu Cloud Archive | Status tracked in Caracal | |||||
| Antelope |
New
|
Undecided
|
Unassigned | |||
| Bobcat |
New
|
Undecided
|
Unassigned | |||
| Caracal |
New
|
Undecided
|
Unassigned | |||
| Ussuri |
New
|
Undecided
|
Unassigned | |||
| Victoria |
New
|
Undecided
|
Unassigned | |||
| Wallaby |
New
|
Undecided
|
Unassigned | |||
| Xena |
New
|
Undecided
|
Unassigned | |||
| Yoga |
New
|
Undecided
|
Unassigned | |||
| Zed |
New
|
Undecided
|
Unassigned | |||
| magnum-ui (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | |||
| Focal |
New
|
Undecided
|
Unassigned | |||
| Jammy |
New
|
Undecided
|
Unassigned | |||
Bug Description
[Impact]
When a cluster template sets fixed_network and fixed_subnet and the user tries to create a new cluster using that template and decides to override the network, the fixed_subnet will inherited from the template, leaving an invalid configuration and later Neutron will refuse to allocate a port (since the subnet doesn't belong to the network). For more details see https:/
[Test Case]
1. Create a new cluster template with a fixed_network test-net and fixed_subnet test-subnet
2. Create a new cluster, uncheck the option "Create new network" and pick a network different from test-net in the dropdown list.
Expected result:
The cluster gets created
Actual result:
The cluster creation fails, because the network configuration is invalid.
| Changed in magnum-ui (Ubuntu): | |
| status: | New → Confirmed |
| Changed in magnum-ui: | |
| assignee: | nobody → Felipe Reyes (freyes) |
| Felipe Reyes (freyes) wrote | #1 |
| Changed in magnum-ui: | |
| status: | New → In Progress |
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/magnum-ui 14.0.0.0rc1 | #2 |
https:/