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

Redis Entra Id connection stops working after 24hours #3554

Open
skbar50 opened this issue Sep 25, 2024 · 3 comments
Open

Redis Entra Id connection stops working after 24hours #3554

skbar50 opened this issue Sep 25, 2024 · 3 comments
Labels
kind/bug Something isn't working

Comments

@skbar50
Copy link

skbar50 commented Sep 25, 2024

Expected Behavior

We started using Entra Id authentication to Redis with the dapr version 1.14.1. We are able to establish the connection from the AKS pod to Redis using the managed identity used by the pod. The pod runs for many days without restarting. It should be able to connect the Redis whenever there is a request from client.

Actual Behavior

However, after running for about 24hours the pod is failing to connect Redis with the error 'State operation failed: the Dapr endpoint indicated a failure. See InnerException for details. Status(StatusCode="Internal", Detail="fail to get PComSearchCacheProduct from state store statestore: ERR WRONGPASS invalid username-password pair") '

Steps to Reproduce the Problem

Run the pod that connects Redis with Entra ID authentication for more then 24hours. It will fail with the above mentioned error after about 24hours.

Additional information

The AKS pod has been working with the same Redis statestore with the password without any issue. We faced this problem when we tried to implement Entra Id authentication.

@skbar50 skbar50 added the kind/bug Something isn't working label Sep 25, 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 25, 2024
@skbar50
Copy link
Author

skbar50 commented Oct 29, 2024

We are still facing the issue. It has not been resolved yet. We need a solution to this.

@github-actions github-actions bot removed the stale label Oct 29, 2024
@yaron2
Copy link
Member

yaron2 commented Oct 30, 2024

/nostale

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

No branches or pull requests

2 participants