2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-09-09 22:46:43 +00:00

fix(mknb): say where the riscv64 loader comes from on Ubuntu

The note shown when boot/grub2/grub2.<arch> is missing told the
administrator it comes from grub2-xcat or the EL installation media. On
Ubuntu neither is true: copycd builds the loader from the grub2 package on
the media, because the image the media carry cannot boot over the network.

Signed-off-by: Vinícius Ferrão <2031761+viniciusferrao@users.noreply.github.com>
This commit is contained in:
Vinícius Ferrão
2026-09-06 00:17:05 -03:00
parent f9baf6e05b
commit c32c941ed7
+3 -3
View File
@@ -907,9 +907,9 @@ sub process_request {
}
}
if (exists $GRUB2_DISCOVERY_ARCHES{$arch} && !-e "$tftpdir/boot/grub2/grub2.$arch") {
# These configurations are only reachable through grub2.<arch>, which xCAT
# does not build.
$callback->({ data => ["Note: $tftpdir/boot/grub2/grub2.$arch is missing; $arch nodes need it to reach these configurations (it is installed by grub2-xcat, or copied from the EL $arch installation media)"] });
# These configurations are only reachable through grub2.<arch>. copycd builds it from
# Ubuntu media; on EL it is supplied by grub2-xcat or copied from the media.
$callback->({ data => ["Note: $tftpdir/boot/grub2/grub2.$arch is missing; $arch nodes need it to reach these configurations (copycd builds it from Ubuntu media; on EL it is installed by grub2-xcat or copied from the $arch installation media)"] });
}
if ($configfileonly && !$s390x_config_error) {
$callback->({ data => ["Write netboot config file done"] });