setting enable_ipmi to false after deployment with enable_ipmi=true does not remove monitors

[Drew Freiberger]

After deploying hw-health checks, I found that the IPMI plugins don't work on my systems, so I ran juju config hw-health enable_ipmi=false, but I still have the following checks alerting:

juju-check-ipmi:
CRITICAL: IPMI Status: Critical [Presence = Critical, vFlash = Critical, BP1 Presence = Critical, BP3 Presence = Critical, BP4 Presence = Critical]

[Paul Henien (phenien)]

Try:
juju config hw-health ipmi_check_options="--noentityabsent "

[Vern Hart (vern)]

Related: Changing enable_ipmi=true after deploying with enable_ipmi=false does not install the appropriate checks.

I was able to get the appropriate things installed by running:

  juju config hw-health enable_ipmi=true enable_ipmiseld=true
  juju run --application hw-health charms.reactive set_flag config.changed.manufacturer
  juju run --application hw-health hooks/config-changed

The same set_flag hack works if I want to return enable_ipmi (or enable_ipmiseld) to false.

[Eric Chen (eric-chen)]

This charm is no longer being actively maintained. Please consider using the new hardware-observer-operator instead. (https://github.com/canonical/hardware-observer-operator)
Therefore, we won't fix this issue.