I am not convinced that CMR is the problem.
I also think "vault relation's interface, secrets-storage, is related but has no units in the relation." message may just be the assess status functions generic interpretation of the incomplete context.
The root problem is VaultKVContext returning incomplete.
TRIAGE:
Since there has been recent work from LP bug#1849323 [1][0] that is the first place we should check.
Setup an environment with vault and nova-compute with encrypt=True related to secrets-storage.
Utilize the refresh-secrets action of vault to kick the secrets-storage relation.
Confirm or dis-confirm bad tokens
Confirm or dis-confirm missing data from non-leader vault nodes
If this does not produce results setup the CMR env.
Initial thoughts and triage
I am not convinced that CMR is the problem.
I also think "vault relation's interface, secrets-storage, is related but has no units in the relation." message may just be the assess status functions generic interpretation of the incomplete context.
The root problem is VaultKVContext returning incomplete.
TRIAGE:
Since there has been recent work from LP bug#1849323 [1][0] that is the first place we should check.
Setup an environment with vault and nova-compute with encrypt=True related to secrets-storage.
Utilize the refresh-secrets action of vault to kick the secrets-storage relation.
Confirm or dis-confirm bad tokens
Confirm or dis-confirm missing data from non-leader vault nodes
If this does not produce results setup the CMR env.
[0] https:/ /github. com/juju/ charm-helpers/ blob/master/ charmhelpers/ contrib/ openstack/ vaultlocker. py#L39 /bugs.launchpad .net/charm- barbican- vault/+ bug/1849323
[1] https:/