...
Once there are no more VMs on that compute node, reinstall the node with AlmaLinux9 using foreman (https://cld-config.cloud.pd.infn.it/users/login)
Go to Hosts → All hosts → cld-np-19.cloud.pd.infn.it
Edit the host in this way:
- The hostgroup must be hosts_all
- The Operating system has to be set to AlmaLinux 9.2 (if the Operating system form doesn't appear, check in the "manage host" option is selected. If not, select it)
- The media (dispositivo) has to be set to AlamLinux AlmaLinux
- The Partion table to be used must be one with LVM thin but with the disks structure you have seen above. Cloud be:
- Kickstart default - swap 128GB - LVM thin (one disk with more partitions)
- Kickstart default - swap 128GB - 2 DISKS - LVM thin (two disks sda with OS and sdb with /var/lib/nova/instances
- Kickstart default - swap 128GB - 2 DISKS NVME - LVM thin (two disks sda with OS and nvme0n1p1 with /var/lib/nova/instances)
- Kickstart default - swap 128GB - 2 DISKS EFI NVME - LVM thin (two disks sda with OS and a biosboot partition for EFI and nvme0n1p1 with /var/lib/nova/instances)
- Kickstart default - swap 128GB - EFI- LVM thin (one disk with more partitions and a biosboot partition for EFI)
- ....
- Kickstart default - swap 128GB - LVM thin (one disk with more partitions)
If there are some missing partition table, one more can be created in foreman web interface, make a clone from the one more similar and change the disk name or size or adding EFI biosboot partition, ....
- Check if the root password is already set otherwise add it.
Save the changes and then build the node. Open a remote console (via https://blade-cld-rmc.lan/cgi-bin/webcgi/login) to reboot the compute
When the node restarts after the update, make sure that SELinux is disabled:
...