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] Deal with shared storage sidecar when fail #19

Open
luiztauffer opened this issue May 13, 2023 · 0 comments
Open

[bug] Deal with shared storage sidecar when fail #19

luiztauffer opened this issue May 13, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@luiztauffer
Copy link
Member

When initializing a Piece in kubernetes and active shared storage, the pod waits for the confirmation of the shared storage's sidecar container initialization. However, if an error occurs during the initialization of this sidecar, no signal is sent to the base container of the pod, causing the pod to be stuck until the timeout (~15min).

To solve this issue, we should check the initialization of the sidecar and, if there is a failure, send an interruption signal to the base container. Additionally, if possible, it is important to provide some kind of log to the user, informing them of what error occurred.

@luiztauffer luiztauffer added the bug Something isn't working label May 13, 2023
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

No branches or pull requests

2 participants