Unable to find implementation for relation: peers of vault-ha
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vault-charm |
Triaged
|
Low
|
Unassigned |
Bug Description
This spurious message comes up often in the charm logs because the metadata.yaml defines a vault-ha peer relation which seems to be entirely unused, and a vault-ha interface layer does not even seem to exist. This message can be confusing and obscure real issues that are causing problems (e.g., see https:/
Possible solutions:
* Remove the unused peer relation
* Create a dummy vault-ha interface layer and include it
The former is less code to maintain, but the latter gives us a place to add implementation if we decide we need some communication between the peers, as well as maintaining the existing relation which will be established on deployed charms (not sure if this is a concern with peer relations or not).
Changed in vault-charm: | |
status: | New → Triaged |
importance: | Undecided → Low |
I can confirm that. 1.juju- log Unable to find implementation for relation: peers of vault-ha
Happens on any deployment. For instance when running functional tests
unit-vault-1: 13:53:51 ERROR unit.vault/
I enclose juju-crashdump.