Workload status should show blocked when no backend is available
Bug #1745971 reported by
Liam Young
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vault-charm |
Fix Released
|
High
|
Liam Young |
Bug Description
Workload status should show blocked when no backend is available. If vault is deployed at the moment without specifying a backend then the vault service is not started but the charm does not appear to be put in a blocked state.
Changed in vault-charm: | |
assignee: | nobody → Liam Young (gnuoy) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in vault-charm: | |
status: | In Progress → Fix Committed |
Changed in vault-charm: | |
milestone: | none → 19.04 |
Changed in vault-charm: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/ /code.launchpad .net/~gnuoy/ vault-charm/ +git/vault- charm/+ ref/bug/ 1745971