-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Refreshing S3 web identity token fails due to missing socket permission #119747
Labels
>bug
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed Coordination
Meta label for Distributed Coordination team
Comments
pxsalehi
added
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>bug
labels
Jan 8, 2025
elasticsearchmachine
added
the
Team:Distributed Coordination
Meta label for Distributed Coordination team
label
Jan 8, 2025
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
pxsalehi
added a commit
to pxsalehi/elasticsearch
that referenced
this issue
Jan 9, 2025
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 9, 2025
…119748) (#119840) Closes #119747 Co-authored-by: Felix Barnsteiner <[email protected]>
pxsalehi
added a commit
to pxsalehi/elasticsearch
that referenced
this issue
Jan 10, 2025
pxsalehi
added a commit
to pxsalehi/elasticsearch
that referenced
this issue
Jan 10, 2025
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 10, 2025
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed Coordination
Meta label for Distributed Coordination team
In #104135, we added support for refreshing web identity credentials when the relevant file on disk is changed. However, the refresh call is not issued with sufficient permissions and it leads to the refresh call failing with:
The current workaround is to restart the affected nodes. The refresh support was added in 8.13.
The text was updated successfully, but these errors were encountered: