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

Disable component-level failure detection for Ray #174

Merged
merged 1 commit into from
Jun 27, 2024

Conversation

dgrove-oss
Copy link
Collaborator

In KubeRay 1.1, status.state == failed is not a stable terminal state, therefore we cannot treat it as a signal to initiate a resetOrFail operation on the AppWrapper.

In KubeRay 1.1, status.state == failed is not a stable terminal state,
therefore we cannot treat it as a signal to initiate a resetOrFail
operation on the AppWrapper.
@dgrove-oss dgrove-oss merged commit eb36ba6 into project-codeflare:main Jun 27, 2024
2 checks passed
@dgrove-oss dgrove-oss deleted the disable-ray-failure branch June 27, 2024 00:19
dgrove-oss added a commit to dgrove-oss/appwrapper that referenced this pull request Jun 27, 2024
)

In KubeRay 1.1, status.state == failed is not a stable terminal state,
therefore we cannot treat it as a signal to initiate a resetOrFail
operation on the AppWrapper.
@dgrove-oss dgrove-oss added the bug Something isn't working label Jun 27, 2024
dgrove-oss added a commit to dgrove-oss/appwrapper that referenced this pull request Jun 27, 2024
)

In KubeRay 1.1, status.state == failed is not a stable terminal state,
therefore we cannot treat it as a signal to initiate a resetOrFail
operation on the AppWrapper.
dgrove-oss added a commit to dgrove-oss/appwrapper that referenced this pull request Jun 27, 2024
)

In KubeRay 1.1, status.state == failed is not a stable terminal state,
therefore we cannot treat it as a signal to initiate a resetOrFail
operation on the AppWrapper.
dgrove-oss added a commit that referenced this pull request Jun 27, 2024
In KubeRay 1.1, status.state == failed is not a stable terminal state,
therefore we cannot treat it as a signal to initiate a resetOrFail
operation on the AppWrapper.
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

Successfully merging this pull request may close these issues.

1 participant