I want to provision ubuntu 22.04 with foreman, but currently the machine boot, ubuntu start to load until it stuck on “reached targed cloud-init target” and then failed beacuse of 10 minute cloud-init timeout Expected outcome:
Ubuntu 22.04 should be installable Foreman and Proxy versions:
currently foreman 3.3 Foreman and Proxy plugin versions:
Distribution and version:
oracle linux 7.9 Other relevant data:
First i patched my 3.3 installation to suport ubuntu 22.04, so this files where modified
Ubuntu returns back to the manual UI-based installation if there is a problem with the User data template - so, I assume there is an error retrieving the template or the template itself is not alright.
The template itself
The 404 regarding vendor-data is not a problem. The important request is the user-data call which should return the User data template you defined for that host. Can you maybe provide the rendered template or check that it is correct yaml?
Retrieving the template
In case you use PXEGrub2 deployment, the template must be set to Preseed default PXEGrub2 Autoinstall. Unfortunately, this template was introduced in Foreman 3.4, but you can just add it from here (please rename the template such that there won’t be any conflict when you upgrade your Foreman.):
It is supposed to be a valid YAML. But, after the updates: security line, the “old” debian-installer commands are injected. This might be due to your partition layout. It must be Preseed default autoinstall - please check your operating system configuration and your host.
Second, the network configuration has an issue as well since it just says the following:
This is not a valid yaml again, due to the fact that the corresponding template relies on a network identifier. This is a design flaw of this respective version of the preseed_netplan_generic_interface snippet.
This can be fixed in two (three) ways:
a) define an identifier for the interface during the host deployment
b) update the snippet to the latest version (introduces MAC-matching instead of identifier-matching)
( c) update to the latest foreman )
I would suggest to try a) first since b) is a bit more complicated (actually 2 templates must be adapted) and c) is just a recommendation but I understand if it is not feasible for you at the moment.
So, going for a): It is important to name the interface according to Ubuntu’s naming scheme according to that machine. For my test machines, it was usually ens160. But, this depends on the hardware. Therefore, I would recommend deploying a machine with this interface name. This is probably gonna result in a host which is not fully deployed due to some netplan error. BUT, when the installer fails, you can actually check the interface name, the Ubuntu installer applies to your hardware. Then, re-deploy the machine with this name.
Thanks a lot for everything, now it’s woking, I need to change a lot of things from the old installer to the new but now that’s ubuntu sh…t
After i finish this upgrade of machines from 18.04 to 22.04 i’ll reinstall foreman from scratch and migrate the hosts. ¿Which is the recomended/suporterted distro moving forward?