6739fa8ef4
Turns out the default VM images have basic support to handle even multipathing. But might not contain the actual bits to enable the kernel initial ramdisk to be regenerated at a later point in time with those artifacts. This creates a situation where a user could deploy the image on a physical host, make other changes or perform an upgrade later, and suddenly loose the ability to boot via multipath. Alternatively, it also creates a situation where resulting DIB images may explicitly loose multipath support where the base image worked just fine. Change-Id: I8e165cf65b1d5db4bcad3264b5c2b098db84fbb8
rhel
Use RHEL cloud images as the baseline for built disk images.
Because RHEL base images are not publicly available, it is necessary
to first download the RHEL cloud image from the Red Hat Customer Portal
and pass the path to the resulting file to disk-image-create as the
DIB_LOCAL_IMAGE environment variable.
The cloud image can be found at (login required): RHEL8: https://access.redhat.com/downloads/content/479/ver=/rhel---8/8.10/x86_64/product-software RHEL9: https://access.redhat.com/downloads/content/479/ver=/rhel---9/9.4/x86_64/product-software
Then before running the image build, define DIB_LOCAL_IMAGE (replace the file name with the one downloaded, if it differs from the example):
export DIB_LOCAL_IMAGE=rhel-9.4-x86_64-kvm.qcow2The downloaded file will then be used as the basis for any subsequent image builds.
For further details about building RHEL images, see the rhel-common and redhat-common element README files.
Environment Variables
- DIB_LOCAL_IMAGE
-
- Required
-
Yes
- Default
-
None
- Description
-
The RHEL base image you have downloaded. See the element description above for more details.
- Example
-
DIB_LOCAL_IMAGE=/tmp/rhel-9.4-x86_64-kvm.qcow2