Workload status should show blocked when no backend is available

Bug #1745971 reported by Liam Young
6
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.

Liam Young (gnuoy)
Changed in vault-charm:
assignee: nobody → Liam Young (gnuoy)
importance: Undecided → High
status: New → In Progress
Revision history for this message
Liam Young (gnuoy) wrote :
James Page (james-page)
Changed in vault-charm:
status: In Progress → Fix Committed
David Ames (thedac)
Changed in vault-charm:
milestone: none → 19.04
David Ames (thedac)
Changed in vault-charm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.