blocked state remains after setting mongodb_uri

Bug #1842362 reported by Paul Collins
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
prometheus-mongodb-exporter-charm
New
Undecided
Unassigned

Bug Description

By design, status-set blocked followed by status-set active does not clear blocked until the next hook is run.

This happens because install_prometheus_mongodb_exporter is called before maybe_monitor_juju_db, which is what triggers the chain of events that results in install_prometheus_mongodb_exporter being called a second time and setting active, which is then too late.

The blocked state is cleared on the next run of the update-status hook, so this isn't the end of the world.

Related branches

Paul Collins (pjdc)
description: updated
Revision history for this message
Paul Collins (pjdc) wrote :

This description is not correct -- in fact, install_prometheus_mongodb doesn't get called again until the next time a hook runs.

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.