You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We tried to update an auditlog service instance which does not seem to be possible. The update failed with message:
"BrokerError:, Status: 400, Description: Updating service is currently not supported operation. Please create a new service with the desired updates and bind to it"
Now we are in a stuck situation, as there is no operation for us to mitigate the update failed state. As a follow-up issue we are unable to create new service bindings for this existing auditlog service instance.
In Kyma a found in BTP Operator logs: 2024-12-12T10:37:30Z INFO controllers.ServiceBinding Service instance with k8s name dsi-auditlog is not ready for binding yet {"servicebinding": {"name":"dsi-auditlog","namespace":"s-management"}, "correlation_id": "2152d7d7-32e2-4579-b92a-86cc1b86d107", "dsi-auditlog": "s-management"} 2024-12-12T10:37:30Z INFO controllers.ServiceBinding setting inProgress conditions: reason: CreateInProgress, message:creation in progress, waiting for service instance 'dsi-auditlog' to be ready, generation: 1 {"servicebinding": {"name":"dsi-auditlog","namespace":"s-management"}, "correlation_id": "2152d7d7-32e2-4579-b92a-86cc1b86d107", "dsi-auditlog": "s-management"}
BTP Operator does not seem to forward the binding request at all because of the service instance update failed situation. As the instance is existing, I do not get the reason for this.
How to move on?
The text was updated successfully, but these errors were encountered:
We tried to update an auditlog service instance which does not seem to be possible. The update failed with message:
"BrokerError:, Status: 400, Description: Updating service is currently not supported operation. Please create a new service with the desired updates and bind to it"
Now we are in a stuck situation, as there is no operation for us to mitigate the update failed state. As a follow-up issue we are unable to create new service bindings for this existing auditlog service instance.
In Kyma a found in BTP Operator logs:
2024-12-12T10:37:30Z INFO controllers.ServiceBinding Service instance with k8s name dsi-auditlog is not ready for binding yet {"servicebinding": {"name":"dsi-auditlog","namespace":"s-management"}, "correlation_id": "2152d7d7-32e2-4579-b92a-86cc1b86d107", "dsi-auditlog": "s-management"} 2024-12-12T10:37:30Z INFO controllers.ServiceBinding setting inProgress conditions: reason: CreateInProgress, message:creation in progress, waiting for service instance 'dsi-auditlog' to be ready, generation: 1 {"servicebinding": {"name":"dsi-auditlog","namespace":"s-management"}, "correlation_id": "2152d7d7-32e2-4579-b92a-86cc1b86d107", "dsi-auditlog": "s-management"}
BTP Operator does not seem to forward the binding request at all because of the service instance update failed situation. As the instance is existing, I do not get the reason for this.
How to move on?
The text was updated successfully, but these errors were encountered: