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

Retry failed deprovision #677

Open
2 tasks
MarekMichali opened this issue Apr 18, 2024 · 0 comments
Open
2 tasks

Retry failed deprovision #677

MarekMichali opened this issue Apr 18, 2024 · 0 comments

Comments

@MarekMichali
Copy link
Contributor

Possible we need to change handling of provisioner errors (at least timeout) in Check_Kyma_Removal step.
In case of timeout we fail deprovisioning.
We do not use here the approach with deprovisioning incomplete, when deprovisioning is retried later on by dedicated job.
Issue: see issue 5388 in internal backlog

After discussion with @piotrmiskiewicz:

  • it was business decision, that in case of provisioner errors we end up with Kyma Runtime in deprovisioning failed state
  • if this is still valid we can consider extending deprovisionerRetrigger job to retry deprovisioning for instances in deprovisioning failed state

AC

  • Deprovision retrigger job tries to deprovision clusters that have status deprovision failed
  • Make it as a configuration option per landascape (enabled/disabled)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant