resources.kube_master_eth0.properties.fixed_ips[0].subnet: Error validating value '': Unable to find subnet with name or id ''
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
New
|
Undecided
|
Unassigned | ||
magnum (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
[Impact]
When creating a new "cluster" based from a "cluster template" that did NOT define the "Fixed Network" and "Fixed Subnet" fields, the cluster creation fails because it couldn't find a subnet for it, this is because the cluster object has its "fixed subnet" property set to `None`.
[Environment]
Focal Ussuri
[Test Case]
1. Create a new cluster template WITHOUT a fixed network/subnet set.
openstack coe cluster template create k8s-cluster-
--image fedora-coreos-32 \
--keypair testkey \
--external-
--flavor m1.small \
--network-
--coe kubernetes
2. Create a new cluster using the template previously created and select an existing network
openstack coe cluster create \
--cluster-
--timeout 120 \
--fixed-network private \
k8scluster
Expected result
The cluster gets created
Actual result:
The cluster creation fails with the following error:
$ openstack coe cluster show k8scluster -f json -c faults | jq -r '.'
{
"faults": {
"default-
"default-
}
}
description: | updated |
summary: |
- cluster creation fails when fixed network and subnet not set in cluster - template + resources.kube_master_eth0.properties.fixed_ips[0].subnet: Error + validating value '': Unable to find subnet with name or id '' |
description: | updated |
Changed in magnum (Ubuntu): | |
status: | New → Confirmed |
Marking as duplicate of 2038109 since they share the same root cause.