Sounds like a second bug here. It shouldn’t need a restart to work after reboot. We should triage and file that bug. Then this would be more cosmetic.
I would expect it to function after a reboot if jujud was disabled.
In terms of hard reboot the juju “start” hook runs on boot. Once upon a time config_changed would also run on boot but that was removed in one of the earlier juju 2.x revisions.
Sounds like a second bug here. It shouldn’t need a restart to work after reboot. We should triage and file that bug. Then this would be more cosmetic.
I would expect it to function after a reboot if jujud was disabled.
In terms of hard reboot the juju “start” hook runs on boot. Once upon a time config_changed would also run on boot but that was removed in one of the earlier juju 2.x revisions.