[Bug] Creating cluster timeout error, reopen #2201

[pkit]

What were you trying to accomplish?

See #2201

What happened?

See #2201

How to reproduce it?

See #2201

Logs

    2022-09-15 16:04:14 [ℹ]  eksctl version 0.105.0
    .....
    2022-09-15 16:15:56 [!]  1 error(s) occurred and cluster hasn't been created properly, you may wish to check CloudFormation console
    2022-09-15 16:15:56 [ℹ]  to cleanup resources, run 'eksctl delete cluster --region=us-east-1 --name=dev'
    2022-09-15 16:15:56 [✖]  error creating Clientset: getting list of API resources for raw REST client: Get "https://3646D4BED90672B70F53263E4BC4CD4B.gr7.us-east-1.eks.amazonaws.com/api?timeout=32s": dial tcp 52.44.60.175:443: i/o timeout

Anything else we need to know? Yes, it still happens in 2022

Versions

$ eksctl info
eksctl version: 0.105.0
kubectl version: v1.23.5
OS: linux

[cPu1]

I have also encountered this and I think I know what the issue is. We'll work on a fix soon.

[rwilson-release]

We also ran into this issue; I think the problem is related to us-east-1 as it is usually pretty busy and has lots of customer workloads in it.

[pkit]

We also ran into this issue; I think the problem is related to us-east-1 as it is usually pretty busy and has lots of customer workloads in it.

It's not an answer. If it times out, eksctl should wait and retry.

[rwilson-release]

It's not an answer. If it times out, eksctl should wait and retry.

Of course! I was only referring to the symptoms, not a solution. 😸

[timharsch]

Also experiencing this issue with m6g.large nodes in us-east-1

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.

[nikolaypopov]

Has this not been fixed? Also having same issue in us-east-1

[rwilson-release]

It is closed from staleness. I think it is still an issue. I would love to try to submit a PR for this which might spur activity.

[timharsch]

/reopen

maybe this will work 🙏

[timharsch]

Apparently not, in my experience, comments on closed issues may be seen in the activity stream but generally are ignored/forgotten. @rwilson-release if you're serious about submitting a PR, I might recommend that you open a new issue and reference this issue for context.

[rwilson-release]

you open a new issue and reference this issue for context

I will do; we have some folks over here who could do it: just a matter of being motivated enough and having enough time to do so.