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

ResolveEndpointV2 error when trying to connect to MSK via IRSA #3551

Open
scosta-kar opened this issue Sep 23, 2024 · 4 comments
Open

ResolveEndpointV2 error when trying to connect to MSK via IRSA #3551

scosta-kar opened this issue Sep 23, 2024 · 4 comments
Labels
kind/bug Something isn't working

Comments

@scosta-kar
Copy link

Creating this issue referencing a bug originally reported in the main dapr repo: dapr/dapr#8122
Issue seems to be a version mismatch in AWS modules

Expected Behavior

PubSub component for kafka (connecting to MSK using IRSA) should just work.

Actual Behavior

time="2024-09-18T17:09:53.885787767Z" level=fatal msg="Fatal error from runtime: process component my-msk-irsa-componen error: [INIT_COMPONENT_FAILURE]: initialization error occurred for my-msk-irsa-componen (pubsub.kafka/v1): [INIT_COMPONENT_FAILURE]: initialization error occurred for my-msk-irsa-componen (pubsub.kafka/v1): error validating iam credentials failed to load credentials: unable to assume role, arn:aws:iam::000000000000:role/my-dapr-role: not found, ResolveEndpointV2\nfailed to load declarative subscriptions: rpc error: code = Canceled desc = context canceled" app_id=my-dapr-app instance=my-dapr-app-7876c8ffb-5l8kx scope=dapr.runtime type=log ver=1.14.4

Steps to Reproduce the Problem

Most likely trying to access MSK using IRSA would result in a repro.

Release Note

RELEASE NOTE:
UPDATE github.com/aws/aws-sdk-go-v2/credentials [v1.17.0]
UPDATE github.com/aws/aws-sdk-go-v2/feature/rds/auth [v1.4.0]
UPDATE github.com/aws/aws-sdk-go-v2/config [v1.27.0]

@scosta-kar scosta-kar added the kind/bug Something isn't working label Sep 23, 2024
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Oct 23, 2024
@joaocc
Copy link

joaocc commented Oct 30, 2024

/remove-lifecycle stale

@github-actions github-actions bot removed the stale label Oct 30, 2024
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Nov 29, 2024
@joaocc
Copy link

joaocc commented Dec 4, 2024

/remove-lifecycle stale

@github-actions github-actions bot removed the stale label Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants