Setup of Backup service fails if Azure-container or S3-bucket are not available yet #627
Description
Steps to reproduce
- Deploy Opensearch with TLS
- Deploy Object storage integrator (either S3 or Azure)
- Relate
Expected behavior
When setting up the Backup service, non-existing S3-buckets / Azure storage containers should be created.
Actual behavior
Setting up the Backup service fails with the following error message (for Azure storage):
unit-opensearch-0: 11:15:14 ERROR unit.opensearch/0.juju-log azure-credentials:6: Failed to setup backup service with exception: HTTP error self.response_code=500
self.response_body={'error': {'root_cause': [{'type': 'repository_verification_exception', 'reason': '[azure-repository] path is not accessible on cluster-manager node'}], 'type': 'repository_verification_exception', 'reason': '[azure-repository] path is not a
ccessible on cluster-manager node', 'caused_by': {'type': 'i_o_exception', 'reason': 'Can not write blob master.dat', 'caused_by': {'type': 'blob_storage_exception', 'reason': 'Status code 404, "\ufeff<?xml version="1.0" encoding="utf-8"?><Error><Code>ContainerN
otFound</Code><Message>The specified container does not exist.\nRequestId:4b3c30c0-501e-001d-390a-b5df13000000\nTime:2025-04-24T11:15:14.0221899Z</Message></Error>"', 'suppressed': [{'type': 'exception', 'reason': '#block terminated with an error'}]}}}, 'status'
: 500}
unit-opensearch-0: 11:15:14 ERROR unit.opensearch/0.juju-log azure-credentials:6: Failed to setup backup service with state Repository exception: unknown