Differences

This shows you the differences between two versions of the page.

--- cluster:171 [2018/08/20 13:34] – [Step 5] hmeij07
+++ cluster:171 [2018/08/20 13:55] (current) – [Step 5] hmeij07
@@ Line 207: / Line 207: @@
 </code>
-Then I have a post boot script that will upgrade the kernel, does something like:
+Then I have a post boot script that will upgrade the kernel. It also does some other actions like updating all users $HOME/.ssh/known_hosts files so that ssh does not choke on old signatures.
 <code>
@@ Line 216: / Line 216: @@
 # staged kernel rpms
 [root@n37 ~]# cd /sanscratch/tmp/rpms
-[root@n37 rpms]# yum install --tolerant *3.10.0*
+[root@n37 rpms]# yum install --tolerant kernel*3.10.0*
 ...
@@ Line 231: / Line 231: @@
 ...
-# reboot from local disk, do not make a golden image of this, stay on 7.2 till 7.5
+# reboot from local disk, do not make a golden image of this
-# is fixed, only add non-kernel packages to vanilla.chroot if needed and re-image
 </code>
@@ Line 238: / Line 237: @@
-As far as I understand it, from CentOS 7.3 and on OHPC/Warewulf switch to GPT disk UEFI boot loader. This involves a boot manager (efibootmgr) that looks not at a master boot record (MBR) on a bootable partition but insteads looks at a file (grubx64.efi). To boot UEFI environment variables need to be supported and you do that in BIOS.  Read the OpenHPC thread "Stateful provisioning with warewulf does not work (ohpc 1.3.5)". You also need to add these packages
+As far as I understand it, from CentOS 7.3 and higher versions, OHPC/Warewulf switch to GPT disk UEFI boot loader. This involves a boot manager (efibootmgr) that looks not at a master boot record (MBR) on a bootable partition but instead looks at a file (grubx64.efi). To boot using UEFI, environment variables need to be supported and you do that in the BIOS.   You also need to add these packages to CHROOT
   * efibootmgr efivar-libs grub2-efi-x64 dosfstools
-My hardware is an ASUS esc4000fdr G2 bought in 2013. In the BIOS boot CSM menus I can set boot filter options to "UEFi and Legacy" and for each type (PXE, Storage,...) I set "UEFI first". These setting allow the CentOS7.2 image to still Legacy PXE boot. Nice.
+My hardware is an ASUS esc4000fdr G2 bought in 2013. In the BIOS boot CSM menus I can set boot filter options to "UEFi and Legacy" and for each type (PXE, Storage,...) I set "UEFI first". These setting still allow the CentOS 7.2 image to still Legacy PXE boot. Nice.
-But the CentOS 7.5 image...not. No matter what settings I use to boot UEFI I continue to receive EFI variables not supported. If I boot the 7.5 image Legacy wise I receive a "can find path to tmpfs error" in mkbootable. The owner of the list thread posted this solution. Look in the deploy script on how to handle that.
+But if I build a CentOS 7.5 image...not. No matter what settings I use to boot UEFI I continue to receive "EFI variables not supported" in the adhoc-postscript step. If I boot the 7.5 image via Legacy boot I receive a "can not find path to tmpfs error" in the mkbootable step.
+The owner of the list thread posted this solution for the UEFI problem. Look in the deploy script on how to handle that.  My work around was to deploy a 7.2 image using a Warewulf stand alone 3.6.99 installation, then update the node kernel. (building a 3.6.99 version [[cluster:139|Warewulf Stateless]]).
@@ Line 254: / Line 255: @@
 [[ -n "$ent" ]] && chroot "$NEWROOT" /usr/sbin/efibootmgr -b "${ent:4:4}" -B
 chroot "$NEWROOT" /usr/sbin/efibootmgr -c -d /dev/sda -l "\EFI\centos\grubx64.efi" -L CentOS-Warewulf
+# Read the OpenHPC thread "Stateful provisioning with warewulf does not work (ohpc 1.3.5)".
 </code>
@@ Line 323: / Line 326: @@
 ==== deploy.txt ====
-File deploy.txt
 <code>