Page History

...

First of all take note of the IP addresses and the interfaces name used by the VM for the management and data networks (192.168.60.x and 192.168.61.x) ) and the relevant interfaces

...

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
• The media (dispositivo) has to be set to AlamLinux
•   (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 AlmaLinux
• The 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)
  • ....

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, ....

When the node restarts after the update, make sure that SELinux is disabled:

• Check if the root password is already set otherwise add it.
• Check if under "Interfaces" the interfaces eno1 and eno2 have the ip (management and data)

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:

[root@cld-np-19 ~]# getenforce 
Disabled

...

If in the compute node there is a dedicated interface (like cld-np-19 eno3) for data lan (use

Use the correct ip and interface name in the commands below )changing the name and ip with yours (change "eno3" and "192.168.61.129")

[root@cld-np-19 ~]#  nmcli con add type ethernet ifname eno3 mtu 9000     (change here the interface name, eno3, with your one)
[root@cld-np-19 ~]#  nmcli con mod eno3 ipv4.method manual ipv4.addr "192.168.61.129/24" (change here the interface name, eno3 and use the corretct ip in data network)
[root@cld-np-19 ~]#  nmcli con up eno3 mod eno3 connection.autoconnect true
[root@cld-np-19 ~]#  nmcli con mod eno3 802-3-ethernet.mtu 9000
[root@cld-np-19 ~]#  nmcli con modup eno3 802-3-ethernet.mtu 9000
[root@cld-np-19 ~]#  ip link set eno3 mtu 9000

...

If the interfaces used the addresses with the tagged network (VLAN 302 andl VLAN 301 in same interface) use these commands (remember to use .

Use the correct IP int ip and interface name the commands below (change "enp2s0f0.302" and "192.168.61.129")

[root@cld-nl-24 ~]#  nmcli con add type vlan ifname enp2s0f0.302 dev enp2s0f0 id 302
[root@cld-nl-24 ~]#  nmcli con mod vlan-enp2s0f0.302 ipv4.method manual ipv4.addr "192.168.61.129/24"
[root@cld-np-24 ~]#  nmcli con up vlan-enp2s0f0.302
[root@cld-np-24 ~]#  nmcli con mod vlan-enp2s0f0.302 802-3-ethernet.mtu 9000
[root@cld-np-24 ~]#  ip link set enp2s0f0 mtu 9000
[root@cld-np-24 ~]#  ip link set enp2s0f0.302 mtu 9000

...

In foreman move the host under the ComputeNode-Prod_Yoga hostgroup.el9  hostgroup

Run puppet manually:

puppet agent -t

...