Custom AMI freezes initialisation of cluster

[d3bt3ch]

trafficstars

When AWSMachineTemplate is provided with a custom ami, even those available through clusterawsadm the cluster creation freezes at WaitingForKubeadmInit

apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
kind: AWSMachineTemplate
metadata:
....
spec:
  template:
    spec:
      ami:
        id: ami-0c6f34a64f2ba7ea6
      instanceType: t3.medium
      ....

EDIT:

Just checked with all the prebuilt images and nothing is working except the Ubuntu images. For all other AMI the initialisation freezes.

❯ clusterawsadm ami list --kubernetes-version v1.27.3 --region us-west-2
KUBERNETES VERSION   REGION      OS               NAME                                         AMI ID
v1.27.3              us-west-2   centos-7         capa-ami-centos-7-v1.27.3-1686976915         ami-007ab2508f82e52b9
v1.27.3              us-west-2   ubuntu-18.04     capa-ami-ubuntu-18.04-v1.27.3-1686976912     ami-0b2b8b55f63f7d59a
v1.27.3              us-west-2   ubuntu-20.04     capa-ami-ubuntu-20.04-v1.27.3-1686976883     ami-02434261db642b2c8
v1.27.3              us-west-2   amazon-2         capa-ami-amazon-2-v1.27.3-1686976919         ami-0c6f34a64f2ba7ea6
v1.27.3              us-west-2   flatcar-stable   capa-ami-flatcar-stable-v1.27.3-1686976923   ami-0d1c474f8eea8a9d1

[k8s-ci-robot]

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/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.