I’d investigate why the log shows this: Cloud-init 19.4 received SIGTERM. Maybe the update task started by cloud-init tries to update cloud-init itself?
@TimoGoebel I assume that I would see something in the logs if that occurs, that it tries to update itself. I haven’t found anything that implies that cloud-init is trying to update itself. Any tips how to exclude your hypothesis if there are no logs pointing that direction?
Many thanks in advance.
Regards,
Hi,
I mentioned it earlier but I deleted some posts, it could be essential.
If I remove /var/cloud/ after a cloud-init failure and reboot the client. Then cloud-init succeeds in running all steps, including installing the packages etc.
Even more strange 1 of 100 tries results in installing all packages etc.
It looks like a race condition with system services, but I could be wrong.
I am updating our image with a later version of cloud-init, that was advised in the cloud-init community for testing purposes.
Regards,
Updated to cloud-init 20.2+137.gc0450c02-1 (Daily build) on CentOS 8 image, and still facing this issue.
I created a bug report on cloud-init with more logs. https://bugs.launchpad.net/cloud-init/+bug/1892902
Regards
1 Like
Get back to us if you find the solution, this is weird.
Dear Lzap,
We have upgraded Foreman and it is working again without any issues, we upgraded from v2.1 to V2.21.
The base image we are using has not been updated or upgraded.
Regards,
1 Like