Livepatch charm "server not running" after machine restart
Bug #2039030 reported by
Yamen Hatahet
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Livepatch On-Prem |
Triaged
|
Medium
|
Unassigned |
Bug Description
After setting up the canonical-
Is it possible to remove the need to manually have to fetch the token every time the host machine restarts?
Running on Channel "latest/stable", with revision "30".
- output of `juju config livepatch`: https:/
To post a comment you must log in.
Hi,
Thanks for the report. It's likely not the case that the get-resource-token action needs to be run again. A few things,
- You can try `juju run-action livepatch/<unit> restart` to restart the server and see if that addresses the issue. In any case though the charm should be starting the server when the machine is restarted so that still needs some investigating. /charmhub. io/canonical- livepatch- server
- Looking at the logs from `juju debug-log` and inside the machine via `juju ssh livepatch/leader` then `journalctl` is there anything indicating why Livepatch can't/was unable to start after the machine was rebooted?
- The charm revision seems out of date, the latest revision in "latest/stable" is "39" as seen here https:/