You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Dragonfly tries to find files in my bucket (which exists and it has permissions to), however it never completes loading the files.
The pod is now 5 days old, so likely it should have completed searching for files now ;-)
To Reproduce
No route for reproduction known
Expected behavior
Dragonfly should not stall upon searching for files. Any aws request should have a deadline and fail eventually if it does not succeed in time. This should then result in a log message printed and the original behavior to be executed (i guess kill the process?).
Screenshots
Environment (please complete the following information):
OS: kubernetes 1.31 on bottlerocket 1.24.0 nodes
Kernel: # Command: 6.1.109
Containerized?: Containerd
Dragonfly Version: 1.23.2
Reproducible Code Snippet
No route for reproduction known
Additional context
This was upon a node being exchanged by another node and not an initial installation, so the s3 file to be searched for do exist.
The text was updated successfully, but these errors were encountered:
Describe the bug
Dragonfly tries to find files in my bucket (which exists and it has permissions to), however it never completes loading the files.
The pod is now 5 days old, so likely it should have completed searching for files now ;-)
To Reproduce
No route for reproduction known
Expected behavior
Dragonfly should not stall upon searching for files. Any aws request should have a deadline and fail eventually if it does not succeed in time. This should then result in a log message printed and the original behavior to be executed (i guess kill the process?).
Screenshots
Environment (please complete the following information):
Reproducible Code Snippet
No route for reproduction known
Additional context
This was upon a node being exchanged by another node and not an initial installation, so the s3 file to be searched for do exist.
The text was updated successfully, but these errors were encountered: