I believe the other two scenarios where config-changed may run are agent returning from down state as well as after a machine reboot. These shouldn't be problematic so long as all hooks are idempotent.
Marco On Tue, Apr 4, 2017 at 11:36 AM Jason Hobbs <jason.ho...@canonical.com> wrote: > I'm trying to understand why config-changed is being triggered on my units > when I'm not changing application config settings. > > From doc/charms-in-action.txt: > > "The `config-changed` hook always runs once immediately after the install > hook, > and likewise after the upgrade-charm hook. It also runs whenever the > service > configuration changes, and when recovering from transient unit agent > errors." > > Why does config-changed run when recovering from transient unit agent > errors? > > Is there anything in the logs I can use to identify recovery from > transient unit agent errors as being the cause of the config-changed hook > running? > > Thanks, > Jason > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
