Comment 8 for bug 1979092

Sorry for taking so long to get around to this one.

@gabrielcocenza and @andersson123: if you run into this again, could you do a leader-get (juju run -u <app>/leader -- leader-get) [or use "juju exec" for juju 3.x] and see what the 'cluster-partition-handling' key is set to. I'd hazard that it is not the same as the config value. The waiting is set by this code:

    if leader_get(CLUSTER_MODE_KEY) != config(CLUSTER_MODE_KEY):
        return (
            'waiting',
            'Not reached target {} mode'.format(CLUSTER_MODE_KEY))

Thanks.