ServiceInstance is not reconciled

[s-lavr]

Hi! We are deploying a Dynatrace service instance and related resources using a Helm chart. Unfortunately, when we deploy the ServiceInstance resource simultaneously with the Entitlement resource (deployed by Crossplane), we encounter the following error:

 ServiceInstance create failed: couldn't find the service offering 'dynatrace' on dataCenter ''

The entitlement takes approximately 15 seconds to become ready, but the ServiceInstance remains stuck in the CreatedFailed state. Is it possible for it to reconcile after a while and self-heal?

We are using the sap-btp-service-operator v0.6.8. In the controller logs, I noticed these messages:

2024-11-27T12:14:01Z    INFO    controllers.ServiceInstance    unable to cast error to SM error, will be treated as non transient    {"serviceinstance": {"name":"dynatrace-dynatrace-instance","namespace":"default"}, "correlation_id": "0f3ae3d8-c2e2-47cf-8d71-8bfdeb42a2d9"}
2024-11-27T12:14:01Z    INFO    controllers.ServiceInstance    operation create of ServiceInstance encountered a non transient error couldn't find the service offering 'dynatrace' on dataCenter '', giving up operation :(    {"serviceinstance": {"name":"dynatrace-dynatrace-instance","namespace":"default"}, "correlation_id": "0f3ae3d8-c2e2-47cf-8d71-8bfdeb42a2d9"}
2024-11-27T12:14:01Z    INFO    controllers.ServiceInstance    updating ServiceInstance status    {"serviceinstance": {"name":"dynatrace-dynatrace-instance","namespace":"default"}, "correlation_id": "0f3ae3d8-c2e2-47cf-8d71-8bfdeb42a2d9"}
2024-11-27T12:14:01Z    INFO    controllers.ServiceInstance    instance is in final state (generation: 1)    {"serviceinstance": {"name":"dynatrace-dynatrace-instance","namespace":"default"}, "correlation_id": "754fb8f6-6c4d-40c0-ba61-aa8e3d9dacba"}
2024-11-27T12:14:01Z    INFO    controllers.ServiceInstance    instance is in final state (generation: 1)    {"serviceinstance": {"name":"dynatrace-dynatrace-instance","namespace":"default"}, "correlation_id": "a2ace259-9769-4cdb-bf36-95c60f4b9a2e"}

[I065450]

Hi @s-lavr

We are discussing this internally and will provide an update soon.

Regards,
Naama

[I065450]

Hi @s-lavr

Could you provide more details about your scenario?
Is it a productive scenario or a testing one?
Additionally, can you separate the two steps: creating the entitlement and creating the service?

Thanks,
Naama

[s-lavr]

Hi Naama!

Yep, sure. We manage our deployments with GitOps and currently have helm chart that deploys all resources needed for Dynatrace instance (entitlement, serviceInstance and ServiceBinding, providerConfig for Dynatrace crossplane provider). When we need to install new Dynatrace instance in subaccount, we just deploy this helm chart and it installs necessary resources. The problem is only with ServiceInstance right now - crossplane resources can reconcile after errors.

It will eventually be used in production environment, but currently it is not.

I think it is possible to separate creating the entitlement and creating the service, but I do not see a benefit of it. It introduces unnecessary complexity and additional deployment step. Absence of entitlement is temporary, I would like for serviceInstance to get transitioned to the desired state eventually.

Thanks!