Failed provision will automatically trigger continous deprovision
qwang1 opened this issue · 8 comments
Hi there,
Posted this issue here: kubevirt/kubevirt-ansible#281
I can reproduce on: openshift v3.10.8, kubevirt v0.7.0, cdi-controller:v1.0.0, asb 1.2.17
My understanding is that this is the result of kubernetes-retired/service-catalog#1248 and not broker specific. @jmrodri or @eriknelson may correct me.
I can confirm this behaviour.
It is expected behavior to get constant deprovisions from the service catalog. That is part of the orphan mitigation of the OSB spec. There is probably something the broker can do to mitigate this situation.
- add some sort of rate limiter with possibly a back off, at some point we would just return error and not create any new pods
- consider a mechanism to handle left around namespaces from failed actions, maybe delete all but the last failed one.
Link to the IRC meeting discussion:
https://github.com/openshift/ansible-service-broker/blob/master/docs/meetings/2018/asbroker.2018-08-07-13.32.log.txt#L75-L114
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/close
@jmrodri: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.