Object Storage Credentials not stored if the main orchestrator is demoted then promoted again without removing object storage relation

[skourta]

If the an OS app is demoted from main orchestrator, s3/azure credentials in the demoted orchestrator is removed, but relation between the object storage integrator still persists. Then when it is promoted again to be the main orchestrator while having object storage relation it will not be able to store the credentials because the events where we do that are never triggered.

Steps to reproduce

1. Deploy large deployment setup
2. Integrate and configure s3-integrator
3. Demote Main orchestrator through relation removal
4. Promote the previously demoted main orchestrator to be the main orchestrator again

Expected behavior

Credentials are stored and passed to the subclusters

Actual behavior

We get a blocked status on the subclusters and the credentials are not stored

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-9064.

This message was autogenerated