Charm shouldn "block" if apply-changes action is configured

Bug #1871856 reported by Peter Sabaini
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
charm-advanced-routing
Won't Fix
Medium
Unassigned

Bug Description

Currently, the charm will always enter "blocking" if it's configured to have changes applied via actions (instead of auto-applying via config-changed), i.e. action-managed-update=True. This is independent of any actual changes to the config pending.

IMHO "blocking" status should be reserved for error conditions or problems, but in this case the charm is within it's normal operating conditions.

Also see https://discourse.juju.is/t/charm-unit-status-and-their-meanings/1168

description: updated
Changed in charm-advanced-routing:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Drew Freiberger (afreiberger) wrote :

My feeling is that "Blocked" means "operator intervention required".

This is congruent with charms blocking waiting for relations (which have to be operator specified to start hitting relation-joined hooks) and vault unseal/init status.

Revision history for this message
Eric Chen (eric-chen) wrote :
Changed in charm-advanced-routing:
status: Confirmed → Won't Fix
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.