Failed to create servicebindings about sap-btp-service-operator HOT 8 CLOSED

There is no such instance in SM.
Just delete the finalizer and the ServiceInstance will be deleted.
Let me know if it happens again sounds like race condition.

from sap-btp-service-operator.

The deletion of serviceinstances also failed with below messages, despite the servicebindings are already deleted:

status:
  conditions:
  - lastTransitionTime: "2021-12-21T10:52:44Z"
    message: |
      ServiceInstance deletion failed: request DELETE https://endpoint/v1/service_instances/a01beab6-289a-432b-b89e-f559d7b01c8a failed: StatusCode: 400 Body: {"error":"BadRequest","description":"could not delete instance due to 1 existing bindings"}
    observedGeneration: 2
    reason: DeleteFailed
    status: "False"
    type: Succeeded
  - lastTransitionTime: "2021-11-19T10:02:57Z"
    message: ""
    reason: Provisioned
    status: "True"
    type: Ready
  - lastTransitionTime: "2021-12-21T10:52:44Z"
    message: |
      ServiceInstance deletion failed: request DELETE https://endpoint/v1/service_instances/a01beab6-289a-432b-b89e-f559d7b01c8a failed: StatusCode: 400 Body: {"error":"BadRequest","description":"could not delete instance due to 1 existing bindings"}
    observedGeneration: 2
    reason: DeleteFailed
    status: "True"
    type: Failed

from sap-btp-service-operator.

Hi,
if you have Failed condition BTP Operator won't retry, we have separation of Transient(retriable) and Non-Transient errors,
But if ServiceInstance doesn't exist considered to be Transient which is strange I'll check it.

I am a bit confused of what happened here:
ServiceBinding failed to be created because ServiceInstance doesn't exist,
and ServiceInstance can't be deleted because ServiceBinding exists for the same instance, binding pair?

from sap-btp-service-operator.

Hi, no they are not the same pair. More over, the creation failure and deletion failure happened in two k8s clusters.
For deletion, we had four clusters with same configuration to be deleted in the same way, three of them were successfully deleted, and only one had the error.

from sap-btp-service-operator.

Hi,
What is this url https://endpoint/v1/service_instances/a01beab6-289a-432b-b89e-f559d7b01c8a doesn't seem like service manager.

Please send me the details I'll check in SM db what happened.

from sap-btp-service-operator.

It is https://service-manager.cfapps.eu10.hana.ondemand.com/v1/service_instances/a01beab6-289a-432b-b89e-f559d7b01c8a

from sap-btp-service-operator.

@pavelmaliy
We often face the issue described in the first post. Typically, we deploy a helm chart with pairs of service instances and bindings. The instance is always created successfully, but frequently, the binding goes into an error state because at the time it checked, the instance was not available yet. Looks to me like a race condition. We solve it by deleting and redeploying just the service binding, but this is a manual effort.

Could you please check again why the BTP operator does not resolve this situation on its own? We are currently using v0.1.16.

from sap-btp-service-operator.

Hi,
I found the problem 404 considered as non transient error will be fixed in this PR
#120

from sap-btp-service-operator.