Occasional stucking of manual provisioning
Bug #1904877 reported by
David
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Hello,
I have seen an issue in the manual provisioning of the charms, that happens very occasionally.
The issue is basically that the charm machine is completely stuck in pending state.
Trying to debug it, I found out that in the cloud.logs there was a message saying there's no cpu-checker candidate. And doing an apt-update the problem was solved.
(Sorry I don't have the logs)
I think that this issue could be solved by checking the provisioning script that juju generates, and probably there's something we could improve there to make it more robust. I imagine that may be the first apt-update is not finishing well... I'm not sure.
summary: |
- Ocasional stucking of manual provisioning + Occasional stucking of manual provisioning |
To post a comment you must log in.
Interesting, when I just provisioned a manual bionic machine, `apt-get update` and `apt-get upgrade` was run.
What are the enable- os-refresh- update and enable-os-upgrade model config values? If both are set to false, juju will not apt update. They are true by default.
What series is the manual machine?
It'd be helpful to have the /var/log/ cloud-init- output. log when this occurs.