Skip to content

fix(k8s): check status before returning error #2279

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

Merged
merged 1 commit into from
Dec 7, 2023

Conversation

Mia-Cross
Copy link
Contributor

The k8s nightly tests currently fail with the error message cluster xxx-xx-xxx has state deleted, wants deleted because the only way to exit the waitK8SClusterDeleted function without an error is with a 404. But sometimes the cluster has state deleted but does not return a 404 right away, prompting this error message.
This can be fixed by checking the status before returning the error.

@Mia-Cross Mia-Cross self-assigned this Dec 7, 2023
@Mia-Cross Mia-Cross added bug k8s Kubernetes Kapsule issues, bugs and feature requests tests labels Dec 7, 2023
@remyleone remyleone added this pull request to the merge queue Dec 7, 2023
Merged via the queue into scaleway:master with commit e0dfe57 Dec 7, 2023
@Mia-Cross Mia-Cross deleted the k8s_fix_delete_error branch December 7, 2023 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug k8s Kubernetes Kapsule issues, bugs and feature requests tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants