LCM does not pass into a waiting state when relation with VCA stops
Bug #1863754 reported by
Dominik Fleischmann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical-OSM |
New
|
Undecided
|
Unassigned | ||
Bug Description
In Charmed OSM HA, when the relation between lcm and osm-vca is removed lcm does not pass into a waiting state. This causes lcm to be still using the old controller when a new osm-vca charm is deployed.
To reproduce this:
1. deploy osm-ha
2. remove-relation between osm-vca and lcm-k8s
3. remove osm-vca offer and application
4. redeploy osm-vca
5. re-add osm-vca and lcm relation
6. When deploying a proxy charm an error will appear due to lcm using the previous controller
Revision history for this message
| David (davigar15) wrote | #1 |
To post a comment you must log in.
TODO: Add health-check in osm-vca charm. If the connection with the controller times out, depart relation.
When the relation is healthy again, configure the lcm pod again (May be new values will be retrieved)