-
Notifications
You must be signed in to change notification settings - Fork 581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load balancer is created but EC2 instances are not created #5282
Comments
This issue is currently awaiting triage. If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
I do not think this is enough information to determine a cause. Can you provide more resources, e.g. Machine, AWSMachine? The CAPA controller logs would also help. Please redact them as necessary. |
|
|
/kind bug
What steps did you take and what happened:
When deploying CAPI workload cluster with existing VPC, the classic load balancer is created but the EC2 instances are
not created. The Machine object is created for the first control plane node but the corresponding instance is not. The Machine object is stuck in Pending. I've tried adding the skip preflight annotation as well.
What did you expect to happen:
After the load balancer is created, the instances for the control plane should spawn and cloud init should bootstrap Kubeadm.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The below error message is logged so I expect the instance should be created. I tried looking for the request via CloudTrail but there doesn't seem to be an event for RunInstances.
Environment:
cluster-api-provider-hetzner version:
clusterctl: v.1.84
clusterapi version v1.9.3
Kubernetes version: (use
kubectl version
)Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.30.5
OS (e.g. from
/etc/os-release
): RHEL 8.10The text was updated successfully, but these errors were encountered: