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] Temporal pods infinite in init state when Elasticsearch has ho username/password auth configured #621

Open
askoriy opened this issue Jan 2, 2025 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@askoriy
Copy link
Contributor

askoriy commented Jan 2, 2025

Describe the bug

After update Temporal to the latest release all pods hung in init state at running check-elasticsearch-index container.
Logs have entries:
waiting for elasticsearch index to become ready

After investigation it found that Elasticsearch return 403 when configured to have no username/password for requests having auth header.

Seems the issue appeared at this commit:
6d50f5d#diff-b8142966d328045abc62158c9a0c7b8492a97eb135757aea4a6941d4a80edb9eR58

Previously helm ommited curl --user argument when no username/password was configured; now the resulted curl command
curl -i --fail --user ":" https://elasticsearch:443/temporal_visibility_v1_dev return 403

Minimal Reproduction

Configure Elasticsearch as visibility storage without username/password authentication.
Deploy temporal helm chart v0.54.0

Temporary workaround

Patch the template to omit entire --user "$ES_USER:$ES_PWD" argument in curl command

@askoriy askoriy added the bug Something isn't working label Jan 2, 2025
@robholland robholland self-assigned this Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants