App not inheriting cluster name in large deployments when --config cluster_name not specified

[smethnani]

Steps to reproduce

1. Deploy main application

juju deploy opensearch main \
   --channel 2/edge \
   --config profile="testing"

2. Deploy second application

juju deploy opensearch failover \
    --config init_hold="true" \
    --config roles="cluster_manager"  \
    --channel 2/edge \
    --config profile="testing"

3. Deploy TLS and integrate

juju deploy self-signed-certificates --config ca-common-name="Test CA"
juju integrate self-signed-certificates main
juju integrate self-signed-certificates failover
juju integrate main:peer-cluster-orchestrator failover:peer-cluster

Expected behavior

The failover app should inherit the cluster name from the main app

Actual behavior

Failover app doesn't inherit cluster name and can't start

App                       Version  Status   Scale  Charm                     Channel        Rev  Exposed  Message
failover                           blocked      1  opensearch                2/edge         204  no       Cannot relate 2 clusters with different 'cluster_name' values.

Versions

Operating system: Ubuntu 24.04

Juju CLI: 3.5.6-genericlinux-amd64

Juju agent: 3.5.5

Charm revision: 204

LXD: 5.21.2 LTS

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

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

This message was autogenerated