If the reboot is happening in the middle of a hook execution, then I don't see any reason why there would be something in the logs.
The uniter writes that it is starting a hook into local state. If the uniter starts up and sees that it had previously started a hook but didn't finish it, it gets marked as an error. This is normal.
Hook executions are generally retried, except update-status.
The update-status hook will execute in five minutes ± jitter after the unit agent has started and connected to the controller.
How are you rebooting the machine?
If the reboot is happening in the middle of a hook execution, then I don't see any reason why there would be something in the logs.
The uniter writes that it is starting a hook into local state. If the uniter starts up and sees that it had previously started a hook but didn't finish it, it gets marked as an error. This is normal.
Hook executions are generally retried, except update-status.
The update-status hook will execute in five minutes ± jitter after the unit agent has started and connected to the controller.
This is expected behaviour.