Activity log for bug #1842362

Date Who What changed Old value New value Message
2019-09-02 22:27:55 Paul Collins bug added bug
2019-09-02 22:28:11 Paul Collins 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 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. 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.
2019-09-02 22:28:20 Paul Collins bug added subscriber The Canonical Sysadmins
2019-09-04 04:49:47 Paul Collins merge proposal linked https://code.launchpad.net/~pjdc/prometheus-mongodb-exporter-charm/+git/prometheus-mongodb-exporter-charm/+merge/372231