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

[BUG] crash-loop status was not assigned to a failed arcane stream #133

Open
yu-tracy opened this issue Oct 11, 2024 · 1 comment
Open
Assignees
Labels
code/bug Something isn't working

Comments

@yu-tracy
Copy link

yu-tracy commented Oct 11, 2024

Description

We had a arcane stream failed because of time out connection. Then ideally its annotations arcane/state should be automatically assigned to crash-loop, but it was not assigned. Could you please check the reason behind and fix it? Thank you very much!

Describe the results you expected

When the arcane stream is failed, it should be in the crash-loop state.

System information

No response

@yu-tracy yu-tracy added the code/bug Something isn't working label Oct 11, 2024
@s-vitaliy s-vitaliy self-assigned this Oct 11, 2024
@s-vitaliy s-vitaliy added this to Arcane Oct 11, 2024
@s-vitaliy
Copy link
Contributor

As a workaround, the failed stream can be suspended and unsuspended.

@s-vitaliy s-vitaliy moved this to Ready in Arcane Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code/bug Something isn't working
Projects
Status: Ready
Development

No branches or pull requests

2 participants