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

[Bug] - MacOS timeout error #6849

Closed
filipponova opened this issue Jul 24, 2023 · 9 comments
Closed

[Bug] - MacOS timeout error #6849

filipponova opened this issue Jul 24, 2023 · 9 comments

Comments

@filipponova
Copy link

What were you trying to accomplish?

When I run any eksctl commands in my Mac M1 Pro (Version 13.4.1 (c) - Ventura) I received the below error:

Error: could not create cluster provider from options: checking AWS STS access – cannot get role ARN for current session: operation error STS: GetCallerIdentity, failed to sign request: failed to retrieve credentials: failed to refresh cached credentials, operation error SSO: GetRoleCredentials, https response error StatusCode: 0, RequestID: , request send failed, Get "https://portal.sso.us-east-1.amazonaws.com/federation/credentials?account_id=XPTO&role_name=XPTO": dial tcp: lookup portal.sso.us-east-1.amazonaws.com: i/o timeout

In my case I'm try run the follow command:

eksctl utils associate-iam-oidc-provider --cluster $CLUSTER_NAME --approve --profile xpto

What happened?

Received timeout error when runs any eksctl commands.

How to reproduce it?

In a Mac running OSX Ventura 13.4.1

1 - Install eksctl (I'm using the version 0.150.0-dev)
2 - Try run any command in macOS. In my case this command: eksctl utils associate-iam-oidc-provider --cluster $CLUSTER_NAME --approve --profile xpto

Logs

Error: could not create cluster provider from options: checking AWS STS access – cannot get role ARN for current session: operation error STS: GetCallerIdentity, failed to sign request: failed to retrieve credentials: failed to refresh cached credentials, operation error SSO: GetRoleCredentials, https response error StatusCode: 0, RequestID: , request send failed, Get "https://portal.sso.us-east-1.amazonaws.com/federation/credentials?account_id=XPTO&role_name=XPTO": dial tcp: lookup portal.sso.us-east-1.amazonaws.com: i/o timeout

Anything else we need to know?

Versions

$ eksctl info

eksctl version: 0.150.0-dev
kubectl version: v1.27.4
OS: darwin
@github-actions
Copy link
Contributor

Hello filipponova 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

@yuxiang-zhang
Copy link
Member

How did you configure your AWS credentials? Please refer to https://eksctl.io/introduction/#prerequisite

@filipponova
Copy link
Author

@yuxiang-zhang, the issue is not related to my credentials, it's the communication between eksctl and the AWS STS API that's causing an issue. When I make requests manually, they are successful, but eksctl returns a timeout.

@filipponova
Copy link
Author

Hello, Folks.

Any updates?

@yuxiang-zhang
Copy link
Member

I cannot reproduce the issue, I suspect it's some conflict in your AWS credentials setup. Notice the URL that's used to fetch the credentials https://portal.sso.us-east-1.amazonaws.com/federation/credentials?account_id=XPTO&role_name=XPTO, the account ID doesn't look correct. Have you set any environment variables related to AWS credentials?

@filipponova
Copy link
Author

I changed my account id to XPTO, just it. I won't paste my account id on internet.

@yuxiang-zhang
Copy link
Member

I'm saying that I need more information so I can try to reproduce. You may need to share how you set up your credentials to help us help you

@github-actions
Copy link
Contributor

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 github-actions bot added the stale label Oct 30, 2023
Copy link
Contributor

github-actions bot commented Nov 5, 2023

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants