stuck in maintenance after no-op upgrade

Bug #1939583 reported by Guillermo Gonzalez
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Telegraf Charm
Fix Released

Bug Description

The charm gets stuck in maintenance status, only when it's related to postgresql *and* prometheus.

Tracked things to a bad reactive state mix, the .unit-state.db ends up with: `reactive.states.prometheus-client.relation.configured` set and `plugins.prometheus-client.configured` unset, this causes it to never execute the configure handler (configure_telegraf_deb or configure_telegraf_snap)

Maybe it's something else, but deleting the `reactive.states.prometheus-client.relation.configured` state from the DB and re-running any hook (update-status) fix things.

Steps to reproduce (tested on xenial)

juju deploy cs:postgresql
juju deploy cs:prometheus2
juju deploy cs:telegraf
juju add-relation telegraf postgresql:juju-info
juju add-relation telegraf postgresql:db
juju add-relation telegraf prometheus2:juju-info
juju add-relation telegraf prometheus2:target
charm pull cs:telegraf
juju upgrade-charm telegraf --path ./telegraf

Related branches

Changed in charm-telegraf:
status: New → Fix Committed
Xav Paice (xavpaice)
Changed in charm-telegraf:
status: Fix Committed → Fix Released
milestone: none → 21.10
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.