-
Notifications
You must be signed in to change notification settings - Fork 84
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
Failed provision will automatically trigger continous deprovision #1010
Comments
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.
|
Link to the IRC meeting discussion: |
Related to Issue #1098 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/close |
@jmrodri: Closing this issue. In response to this:
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. |
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
The text was updated successfully, but these errors were encountered: