-
Notifications
You must be signed in to change notification settings - Fork 16
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
AWS prepare without credentials present fails due to no EC2 IMDS role found
#297
Comments
no EC2 IMDS role found
no EC2 IMDS role found
This is caused by submariner-io/submariner-operator#1783 which delegates the configuration handling to the AWS SDK. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
faced the same issue while trying with aws today.
It worked after using the correct profile(using the --profile tag) from the
|
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
Seems like this would still be an issue. Not a big failure likely, just bad UX around the message. Still, it seems users are hitting it. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
What happened:
Running cloud prepare for AWS via
subctl
, when no~/.aws/credentials
file is found, fails with:What you expected to happen:
It should present a clear error message
On 0.11.2 it used to present this message:
How to reproduce it (as minimally and precisely as possible):
Install openshift on AWS using openshift-installer:
./openshift-install create cluster
Run cloud prepare:
subctl cloud prepare aws
Anything else we need to know?:
Environment:
subctl diagnose all
):subctl gather
):devel
and on0.12.1
The text was updated successfully, but these errors were encountered: