Charm raises a BlockedState when certificates relation is not yet ready
Bug #2031560 reported by
Mateo Florido
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes API Load Balancer |
Fix Committed
|
Medium
|
Mateo Florido | ||
Bug Description
The Kubernetes API Load Balancer charm triggers a `BlockedState` when the certificates relation is not yet ready. We should enhance its handling of this check by employing a more robust method to differentiate between the various states of the certificates relation. This will ensure that the appropriate state is raised in each specific case.
| Changed in charm-kubeapi-load-balancer: | |
| status: | New → In Progress |
| Changed in charm-kubeapi-load-balancer: | |
| status: | In Progress → Fix Committed |
| importance: | Undecided → Medium |
| assignee: | nobody → Mateo Florido (mateoflorido) |
To post a comment you must log in.
