Rocky Linux 10.0 Provisioning

Problem:

Unable to provision Rocky Linux 10.0. After vmlinuz and initrd are loaded, kickstart provisioning does not start. Instead, host reboots with foreman discovery again, in a continuous loop.

This is the first Rocky 10 release. Does Foreman fully support provisioning Rocky 10 hosts?

Expected outcome:

Rocky Linux 10.0 installation using Kickstart templates

Foreman and Proxy versions:

Foreman 3.15
Foreman Proxy 3.15

Foreman and Proxy plugin versions:

foreman_discovery 26.0.0
foreman_puppet 8.1.1

Distribution and version:

Rocky Linux 9.6
Puppetserver 8.7
Puppet-agent 8.10

Other relevant data:

Provisioning templates:

  • Kickstart default
  • Kickstart default finish
  • Kickstart default PXELinux

I’ve got Rocky 10 provisioning working via kickstart on a Foreman 3.14 Rocky 9.6 node host.

What does the production log show ? one thing I noticed when I moved to provisioning 9.6 and 10 nodes was my first boot of a guest failed (with a kernel panic, unable to sync rootFS) yet the second boots worked and and every subsequent build worked after that, I’ve not looked into why that was yet.

the obvious things to check are the size of the files in the tftpboot directory, are they there and the right sizes, did they download correctly (re-select build on the host and watch the production log to see if it gets the right files to download)

How do you look at the production log — Where is it located?

/var/log/foreman normally

I was trying to provision Rocky 10 on an ancient box with a Xeon “Westmere-EP” CPU (circa 2011.) After reading in the release notes that Rocky 10 requires x86-64-v3 or later, I tried provisioning on a newer box with a Xeon “Ice Lake” CPU (circa 2022.) Lo and behold, anaconda starts running and gets all the way up to disk partitioning, where it barfs with this error:

Your BIOS-based system needs a special partition to boot from a GPT disk label. To continue, please create a 1MiB 'biosboot' type partition on the vda disk.

So, I added this line to my partition table, before the actual ‘/boot’ partition:

part biosboot --fstype=biosboot --size=1

after which anaconda provisioning runs to completion.

So, now I have a fully-provisioned Rocky 10.0 host — with no Puppet agent! At this time, Puppet Labs has not yet announced EL10 support. Some day soon, hopefully.

1 Like

Very unlikely, I would look into OpenVox Automation Framework as alternative.

2 Likes

May not be a bad thing. Ansible all the way :grin: