You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
Executing clusterctl generate cluster --flavor flatcar-sysext results in a cluster failing with FloatingIPError.
$ clusterctl describe cluster test
NAME READY SEVERITY REASON SINCE MESSAGE
Cluster/test False Error FloatingIPError @ Machine/test-control-plane-tvr7h 41m 0 of 1 completed
├─ClusterInfrastructure - OpenStackCluster/test
└─ControlPlane - KubeadmControlPlane/test-control-plane False Error FloatingIPError @ Machine/test-control-plane-tvr7h 41m 0 of 1 completed
└─Machine/test-control-plane-tvr7h False Error FloatingIPError 41m Obtaining management port for control plane machine failed: lookup management port for server 7d8c04 ...
The IP is pulled from the pool and assigned to the OpenStackCluster resource, but never actually assigns to anything.
This issue does not occur when using no --flavor. The only differences between no flavor (w/ Ubuntu) and using flatcar-sysext (w/ Flatcar) are the Flatcar-specific additions, and a lack of apiServerLoadBalancer in the Flatcar OpenStackCluster resource. Once I add that into a generated cluster yaml and apply it, the cluster comes back operational.
What did you expect to happen:
Work right out of the box without having to add anything.
Anything else you would like to add:
The spec: apiServerLoadBalancer portion is configured for deletion here, which is actively causing the issue.
Environment:
Cluster API Provider OpenStack version (Or git rev-parse HEAD if manually built): latest
/kind bug
What steps did you take and what happened:
Executing
clusterctl generate cluster --flavor flatcar-sysext
results in a cluster failing withFloatingIPError
.The IP is pulled from the pool and assigned to the OpenStackCluster resource, but never actually assigns to anything.
This issue does not occur when using no
--flavor
. The only differences between no flavor (w/ Ubuntu) and using flatcar-sysext (w/ Flatcar) are the Flatcar-specific additions, and a lack ofapiServerLoadBalancer
in the FlatcarOpenStackCluster
resource. Once I add that into a generated cluster yaml and apply it, the cluster comes back operational.What did you expect to happen:
Work right out of the box without having to add anything.
Anything else you would like to add:
The
spec: apiServerLoadBalancer
portion is configured for deletion here, which is actively causing the issue.Environment:
git rev-parse HEAD
if manually built): latestclusterctl version: &version.Info{Major:"", Minor:"", GitVersion:"1.8.4", GitCommit:"brew", GitTreeState:"clean", BuildDate:"2024-10-08T05:24:23Z", GoVersion:"go1.23.2", Compiler:"gc", Platform:"darwin/amd64"}
kubectl version
): 1.31/etc/os-release
): Flatcar 3975.2.1The text was updated successfully, but these errors were encountered: