Closed bashadude closed 3 months ago
is your hardware supported by Alma 8.8?
MAAS runs the efibootmgr
supplied by the target OS, so often this kind of error is caused by incompatibilities between your OS and the HW
Firstly, Thanks For Reply @alexsander-souza
It was supported my manually. Through MaaS we are not able to do that. Can you tell me why?
we tried going through to the epherimal image and check mount partition and ran efibootmgr --create --write-signature --label redhat --disk /dev/nvme0n1 --part 1 --loader /EFI/redhat/shimx64.efi --verbose
It appeared same error.
Are you running MAAS 3.4? snap or deb?
with MAAS 3.4, we can test if the CentOS quirks are enough.
when uploading your custom image, use name='centos/alma8'
instead of name='custom/alma8'
. this is going to trick MAAS into enabling a few quirks that might help you.
with MAAS 3.4, we can test if the CentOS quirks are enough.
when uploading your custom image, use
name='centos/alma8'
instead ofname='custom/alma8'
. this is going to trick MAAS into enabling a few quirks that might help you.
we are using MaaS 3.3.5 @alexsander-souza I will that name=centos/alma8. Let you know
with MAAS 3.4, we can test if the CentOS quirks are enough. when uploading your custom image, use
name='centos/alma8'
instead ofname='custom/alma8'
. this is going to trick MAAS into enabling a few quirks that might help you.we are using MaaS 3.3.5 @alexsander-souza I will that name=centos/alma8. Let you know
it's not working @alexsander-souza it was giving same issue
It was worth a try, MAAS 3.4.0 sets some kernel flags that have helped other distros in the past with similar errors.
I think this can be fixed by patching Curtin as suggested here https://bugs.launchpad.net/curtin/+bug/1922970/comments/3.
/EFI/redhat/shimx64.efi
does not exist, instead it should be /EFI/almalinux/shimx64.efi
, the corresponding code that breaks the installation is here https://git.launchpad.net/curtin/tree/curtin/commands/install_grub.py#n283 because the bootid
variable is set to redhat instead of almalinux.
I confirm I am getting the same error. This is one of the cases that we need to wait for the curtin fixes to be merged with MAAS in order to fix.
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: FAIL: installing grub to target devices
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: FAIL: configuring target system bootloader
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command curthooks
Traceback (most recent call last):
File "/curtin/curtin/commands/main.py", line 202, in main
ret = args.func(args)
File "/curtin/curtin/commands/curthooks.py", line 1886, in curthooks
builtin_curthooks(cfg, target, state)
File "/curtin/curtin/commands/curthooks.py", line 1851, in builtin_curthooks
setup_grub(cfg, target, osfamily=osfamily,
File "/curtin/curtin/commands/curthooks.py", line 804, in setup_grub
install_grub(instdevs, target, uefi=uefi_bootable, grubcfg=grubcfg)
File "/curtin/curtin/commands/install_grub.py", line 401, in install_grub
in_chroot.subp(cmd, env=env, capture=True)
File "/curtin/curtin/util.py", line 787, in subp
return subp(*args, **kwargs)
File "/curtin/curtin/util.py", line 275, in subp
return _subp(*args, **kwargs)
File "/curtin/curtin/util.py", line 139, in _subp
raise ProcessExecutionError(stdout=out, stderr=err,
curtin.util.ProcessExecutionError: Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmphq0fky3a/target', 'grub2-mkconfig', '-o', '/boot/efi/EFI/redhat/grub.cfg']
Exit code: 1
Reason: -
Stdout: ''
Stderr: /usr/sbin/grub2-mkconfig: line 278: /boot/efi/EFI/redhat/grub.cfg.new: No such file or directory
Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmphq0fky3a/target', 'grub2-mkconfig', '-o', '/boot/efi/EFI/redhat/grub.cfg']
Exit code: 1
Reason: -
Stdout: ''
Stderr: /usr/sbin/grub2-mkconfig: line 278: /boot/efi/EFI/redhat/grub.cfg.new: No such file or directory
Ran another quick test with Oracle Linux, getting a very similar error:
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: FAIL: installing grub to target devices
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: FAIL: configuring target system bootloader
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command curthooks
Traceback (most recent call last):
File "/curtin/curtin/commands/main.py", line 202, in main
ret = args.func(args)
File "/curtin/curtin/commands/curthooks.py", line 1886, in curthooks
builtin_curthooks(cfg, target, state)
File "/curtin/curtin/commands/curthooks.py", line 1851, in builtin_curthooks
setup_grub(cfg, target, osfamily=osfamily,
File "/curtin/curtin/commands/curthooks.py", line 804, in setup_grub
install_grub(instdevs, target, uefi=uefi_bootable, grubcfg=grubcfg)
File "/curtin/curtin/commands/install_grub.py", line 401, in install_grub
in_chroot.subp(cmd, env=env, capture=True)
File "/curtin/curtin/util.py", line 787, in subp
return subp(*args, **kwargs)
File "/curtin/curtin/util.py", line 275, in subp
return _subp(*args, **kwargs)
File "/curtin/curtin/util.py", line 139, in _subp
raise ProcessExecutionError(stdout=out, stderr=err,
curtin.util.ProcessExecutionError: Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmpqyk9rl5j/target', 'grub2-mkconfig', '-o', '/boot/efi/EFI/fedora/grub.cfg']
Exit code: 1
Reason: -
Stdout: ''
Stderr: /usr/sbin/grub2-mkconfig: line 278: /boot/efi/EFI/fedora/grub.cfg.new: No such file or directory
Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmpqyk9rl5j/target', 'grub2-mkconfig', '-o', '/boot/efi/EFI/fedora/grub.cfg']
Exit code: 1
Reason: -
Stdout: ''
Stderr: /usr/sbin/grub2-mkconfig: line 278: /boot/efi/EFI/fedora/grub.cfg.new: No such file or directory
By the way, I am running MAAS 3.3.6. Oracle Linux support is clearly marked as MAAS 3.5+. If the Curtin fix would not land on MAAS 3.3, we should perhaps update the README since it is currently static Alma is supported with MAAS 3.3+
If you can't wait for MAAS 3.5 or have to use an older version, this one line Kickstart hack makes it work:
$ git diff ol9/ alma9/
diff --git a/alma9/http/alma9.ks.pkrtpl.hcl b/alma9/http/alma9.ks.pkrtpl.hcl
index 3d8df2e..73c4010 100644
--- a/alma9/http/alma9.ks.pkrtpl.hcl
+++ b/alma9/http/alma9.ks.pkrtpl.hcl
@@ -85,6 +85,9 @@ chmod 440 /etc/sudoers.d/alma
#### fix up selinux context
# restorecon -R /home/alma/.ssh/
+#LP 2009240
+mv -v /boot/efi/EFI/almalinux /boot/efi/EFI/redhat
+
%end
%packages
Hi, Guys Can you please help me to solve this issue. @bjornt @sparkiegeek @ltrager @niemeyer @alexsander-souza
Stderr: ''