deployed application loses trust after charm upgrade
Bug #1940526 reported by
James Page
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Harry Pidcock |
Bug Description
Charm: RabbitMQ operator
Juju: 2.9.9
I'm working on enabling clustering using the native K8S support in RMQ to support peer discovery, which is working nicely; I use juju trust to allow the units to access information directly in K8S supporting this method in RMQ.
This all worked fine until I upgraded the charm to a new version; post upgrade, all of the RMQ units loose access to the K8S API with a 403 forbidden being returned, and hence fail to re-join the cluster in turn.
I'll try upgrading to 2.9.x latest.
summary: |
- deployed application looses trust after charm upgrade + deployed application loses trust after charm upgrade |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Harry Pidcock (hpidcock) |
Changed in juju: | |
milestone: | 2.9-next → 2.9.17 |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
So to confirm the issue that you are seeing, if you 'juju trust' a given deployed charm, then when you upgrade the charm it ends up losing the credentials in the upgraded application.