Skip to content
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

EKS cluster AWSMachines not created because MachineSet pre-fight check fails #5225

Open
tingchienc opened this issue Nov 22, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@tingchienc
Copy link

tingchienc commented Nov 22, 2024

/kind bug

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

Add a MachineDeployment for the EKS cluster deployed by CAPA
No errors in the capa-controller pods

But there is an error for the machineDeployment.

Error messages:
Message: Performing "Scale up" on hold because ControlPlane namespace/cluster-control-plane is provisioning ("ControlPlaneIsStable" preflight failed). The operation will continue after the preflight check(s) pass

After we set the annotation "machineset.cluster.x-k8s.io/skip-preflight-checks: ControlPlaneIsStable", the EC2 machines finally created.

The problem is why the preflight-checks fail? We don't want to add the annotation for every MachineDeployment.
And it seems like a new feature added in Sep by ClusterAPI.

What did you expect to happen:
EC2 machines created without adding the annotation

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-aws version: latest
  • Kubernetes version: (use kubectl version): 1.29.0
  • OS (e.g. from /etc/os-release): ubuntu
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-priority labels Nov 22, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants