Comment 3 for bug 1915573

The Ubuntu kernel/initrd in the stream is only used for booting. During deployment a kernel is installed from the archive and the initrd is generated for the target system. The initrd generated for the target system only has the required kernel modules for that system, not all kernel modules.

gh:canonical/packer-maas has to include a kernel in the CentOS image which generates an initrd at image build time. There isn't a way with kickstart to include additional modules without permanently including in the initrd. We also don't have a good way of know which kernel modules should be included as I have access to a limited test environment. This environment doesn't have NVME hardware in it so while I know some kernel modules are missing for NVME I don't know which ones are missing. There may be other storage drivers missing that I'm unaware of because I don't have access to test hardware.

Why not always regenerate the initrd on CentOS/RHEL installation? This should leverage the scripts in CentOS to pull in the appropriate drivers automatically.