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

[Core] Receiving RuntimeEnvSetupError frequently after migrating from 2.3.0 to 2.20.0 #45311

Closed
raghumdani opened this issue May 13, 2024 · 1 comment
Labels
bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@raghumdani
Copy link

What happened + What you expected to happen

We recently migrated Ray version from 2.3.0 to 2.20.0 and are seeing RuntimeEnvSetupError more frequently however we weren't seeing the same error before.

Stack Trace:

Failed to create runtime env for job 02000000, status = IOError: on_read bad version, maybe there are some network problems, will fail the request.

Versions / Dependencies

Ray: 2.20.0
Python: 3.10
OS: Ubuntu 20.04

Reproduction script

Issue Severity

None

@raghumdani raghumdani added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels May 13, 2024
@anyscalesam anyscalesam added the core Issues that should be addressed in Ray Core label May 20, 2024
@rynewang
Copy link
Contributor

Duplicate for #45353

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

3 participants