Installing Rocky Linux 9.2 on baremetal - Missing group or modules @core

I have been troubleshooting a weird issue since past week and wondering if someone here can help. I am trying to install Rocky Linux 9.2 (will upgrade to 9.4 later) via my company’s 9.2 approved ISO file on DL360 HP server through iLO. I am then building my custom repo and specifying it in kickstart file and regenerating the ISO again using genisoimage utility.

I have the following lines specified in my kickstart file:

repo --name="BaseOS" --baseurl=file:///run/install/repo/BaseOS/ --install
repo --name="AppStream" --baseurl=file:///run/install/repo/AppStream/
repo --name="custom-9.2-repo" --baseurl=file:///run/install/repo/custom-9.2-repo/

%packages
@core

%end

# Install RPMs useful in troubleshooting
%packages
telnet
wget
curl
tcpdump
traceroute

%end

Seems like the installer is finding these repos (all three) and downloading the required repomd.xml and other xml files in /tmp/dnf.cache folder but then it complains about missing groups or modules: @core. If I continue the installation, it does install all packages from my custom repo but for some reason it is not installing @core packages.

I am at a complete loss here and trying to understand what can be done for the installer to find @core. Since it is installing telnet, wget, curl, etc. that tells me it was able to find my custom repo. I am not touching BaseOS and AppStream repos from the original ISO.

Contents of the folder before I generate ISO file:

-rw-r--r--  1 root root  1522 May 12  2023 .treeinfo
-rw-r--r--  1 root root    46 May 12  2023 .discinfo
-r--r--r-- 1 root root  2204 Apr 27  2023 LICENSE
dr-xr-xr-x 3 root root    18 May 12  2023 EFI
dr-xr-xr-x 3 root root    59 May 12  2023 images
-r--r--r-- 1 root root  3159 May 12  2023 RPM-GPG-KEY-Rocky-9-Testing
-r--r--r-- 1 root root  1750 May 12  2023 RPM-GPG-KEY-Rocky-9
-r--r--r-- 1 root root   372 May 12  2023 EULA
-r--r--r-- 1 root root  1394 May 12  2023 Contributors
-r--r--r-- 1 root root  5504 May 12  2023 COMMUNITY-CHARTER
-r--r--r-- 1 root root   102 May 12  2023 media.repo
dr-xr-xr-x 4 root root    38 Oct 31  2023 BaseOS
dr-xr-xr-x 4 root root    38 Oct 31  2023 AppStream
dr-xr-xr-x 2 root root   318 Dec 18 21:25 isolinux
drwxr-xr-x 3 root root 20480 Dec 19 15:13 custom-9.2-repo
-rw-r--r-- 1 root root  7105 Dec 21 04:36 ks.cfg

I recommend using xorriso if you’re trying to add content to the ISO, as you can simply add files without unpacking the ISO and it can help keep the same integrity (like isohybrid).

# Change X-Y to the version of release, e.g. 9-5
xorriso -indev <input iso> \
  -outdev <output iso> \
  -boot_image any replay \
  -joliet on \
  -system_id LINUX \
  -compliance joliet_long_names \
  -volid Rocky-X-Y-x86_64-dvd \
  -map /path/to/custom-repo/repodata/...
  -map /path/to/custom-repo/some_package.rpm
. . .

We do this when making our DVD’s, as we take the initial boot.iso and use similar arguments above.

% cat dialog
-indev /mnt/compose/9/latest-Rocky-9/work/lorax/x86_64/lorax/images/boot.iso
-outdev Rocky-9.5-x86_64-dvd.iso
-boot_image any replay
-joliet on
-system_id LINUX
-compliance joliet_long_names

-volid Rocky-9-5-x86_64-dvd
-update /mnt/compose/9/latest-Rocky-9/work/lorax/x86_64/dvd/EFI/BOOT/grub.cfg EFI/BOOT/grub.cfg
-update /mnt/compose/9/latest-Rocky-9/work/lorax/x86_64/dvd/images/efiboot.img images/efiboot.img
-update /mnt/compose/9/latest-Rocky-9/work/lorax/x86_64/dvd/isolinux/isolinux.cfg isolinux/isolinux.cfg
-update /mnt/compose/9/latest-Rocky-9/work/lorax/x86_64/dvd/.discinfo .discinfo
-map /mnt/compose/9/latest-Rocky-9/work/lorax/x86_64/dvd/.treeinfo .treeinfo
-map /mnt/compose/9/latest-Rocky-9/compose/AppStream/x86_64/os/repodata/2901b268bc43f796b5c6d74c9ec9dd693f81dc17e7c3868f68b3bc604226022b-other.sqlite.gz AppStream/repodata/2901b268bc43f796b5c6d74c9ec9dd693f81dc17e7c3868f68b3bc604226022b-other.sqlite.gz
. . .
-end

% cat buildExtraImage-x86_64-dvd.sh
. . .
/usr/bin/xorriso -dialog on < dialog

I recommend using 9.5 as that is the only version supported for Rocky Linux 9.

1 Like

Thanks, xorriso didn’t work either. Seems like my company did something when they built the ISO for us, I went ahead and used Rocky’s minimal ISO and repackaged everything as I wanted and it seemed to have done the trick.

It’s still a mystery why my company’s ISO would not work to locate @core groups or module.