Revert "[release] Update Ray image to 2.34.0 (#2303)" #2413
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 678ec25.
MortalHappiness
approved these changes
Sep 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit 678ec25.
Ray 2.10 or 2.11 (ray-project/ray#44658) introduces a bug where the dashboard agent process gets stuck if a Ray job is created, causing the readiness/liveness probes set by KubeRay to fail. It is fixed by ray-project/ray#47721. However, it is not cherry-picked to Ray 2.37.0, so I decided to revert to Ray 2.9.0 for now. I will set it to Ray 2.38.0 after Ray Summit.
Why are these changes needed?
Related issue number
Checks