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.

Sign up for GitHub

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

Jump to bottom

incorrect handling of degraded applications #304

Open

shini4i opened this issue May 23, 2024 · 1 comment

Labels

bug

Owner

shini4i commented May 23, 2024 •

edited

Loading

I've noticed that we are stuck in a semi-infinite loop in the following scenario:

Initial deployment led to the degraded app
A new task was triggered with a different image that failed to deploy again
Starting from the second deployment, our timeout starter to work incorrect, and the task was aborted more than 20 minutes after it should have

All further deployment tasks were marked as failed within 40 to 60 minutes, while the timeout was set to 30.

Affected version: v0.8.4

shini4i added the bug label

Owner Author

shini4i commented May 23, 2024

In addition to the information above, as soon as the deployment of the fixed application was started, the timeout began to work correctly again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment