-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
Testable
-
-
Through a recent heads up from Matus Marhefka we found out that not only is the behavior of Anaconda working with the DVD source not properly documented, but it also differs in behavior between RHEL 9 and RHEL 10. To capture the current knowledge:
For a kickstart that has no installation source specification and is otherwise complete, Anaconda will start automatic installation if:
- the installation is started from a DVD image (from virtual CDROM or flash drive)
- installation is started from boot.iso but a DVD image is also available (from virtual CDROM or flash drive)
This behavior seems to be consistent across both RHEL 9 & 10, both VMs and baremetal (tested on a spare laptop).
What differs is the behavior if the kickstart being used has the ignoredisk --only-use (e.g.: ignoredisk --only-use=sda):
- if the DVD image is on a SATA CDROM then behavior is the same as before
- if the DVD image is on USB CDROM or USB flash drive, Anaconda fails to automatically find & use the installation source on RHEL 9 only
(What likely happens is that SATA CDROM end up on /dev/sr0 and that shortcuts the installation source detection. USB CDROM and USB flash drives end up as /dev/sd<letter> and get filtered out with regular storage devices.)
In general this is likely correct behavior, should be properly documented for RHEL 9 & 10 and most importantly covered by our integration tests. Thankfully, this should be doable via kickstart tests, with possibly some tweaks for working with the rather big DVD images.
Scenarios we need to cover:
- RHEL 9 installation starts for a kickstart that has no installation source specification and is otherwise complete
- RHEL 10 installation starts for a kickstart that has no installation source specification and is otherwise complete
- RHEL 10 installation starts for a kickstart that has no installation source specification and is otherwise complete and has ignoredisk --only-use=vda
- RHEL 9 installation does not start for a kickstart that has no installation source specification and is otherwise complete and has ignoredisk --only-use=vda
- this might require the test to be marked as known-failure or to be manual triggered or support for automatically running kickstart tests that fail in a specific way
This way we should be able to spot changes in behavior that we might otherwise miss when we change payload on storage code.
- is blocked by
-
INSTALLER-4231 Make it possible to add additional installation media to a test run
-
- New
-