-
Notifications
You must be signed in to change notification settings - Fork 70
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
Investigate org deletion timeout in smoke tests #3061
Labels
Comments
georgethebeatle
added a commit
that referenced
this issue
Jan 15, 2024
…imeout Print cforg namespace in fail handler
This was referenced Mar 13, 2024
danail-branekov
added a commit
that referenced
this issue
Mar 19, 2024
Smoke tests have been failing frequently because org deletion times out. Previous debug output showed that the timeout is caused by org namespace being not deleted because of app pods do not disappear and remaining pods are in phase `Pending` (e.g. see https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/deploy-korifi-acceptance/builds/802) We have found a [k8s bug report](kubernetes/kubernetes#121435) that pending pods cannot be deleted. We suspect that in those cases the cluster is just being slow. In order to workaround that bug, we simply ignore the org deletion exit code as org deletion is not really in the focus of the smoke tests. Org deletion is covered in details by e2e tests. Also, delete the related debug logs as they are not needed anymore. fixes #3061 Co-authored-by: Danail Branekov <danailster@gmail.com>
danail-branekov
added a commit
that referenced
this issue
Mar 19, 2024
Smoke tests have been failing frequently because org deletion times out. Previous debug output showed that the timeout is caused by org namespace being not deleted because of app pods do not disappear and remaining pods are in phase `Pending` (e.g. see https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/deploy-korifi-acceptance/builds/802) We have found a [k8s bug report](kubernetes/kubernetes#121435) that pending pods cannot be deleted. We suspect that in those cases the cluster is just being slow. In order to workaround that bug, we simply ignore the org deletion exit code as org deletion is not really in the focus of the smoke tests. Org deletion is covered in details by e2e tests. Also, delete the related debug logs as they are not needed anymore. fixes #3061 Co-authored-by: Danail Branekov <danailster@gmail.com> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
github-project-automation
bot
moved this from 🔄 In progress
to ✅ Done
in Korifi - Backlog
Mar 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Smoke tests are occasionally failing in
AfterSuite
with org deletion timeout. Let's investigate what is causing this.The text was updated successfully, but these errors were encountered: