What were you trying to do that didn't work?
--> Install RHEL using Anaconda with an NFS installation source defined via Kickstart. When the NFS or installation source is unreachable or incorrectly specified, the installer does not report any error and fails to proceed.
What is the impact of this issue to you?
--> The installer gets stuck in an infinite loop at “Checking storage configuration” with no user-visible error message, blocking the installation and making troubleshooting difficult.
Please provide the package NVR for which the bug is seen:
--> Anaconda instraller
How reproducible is this bug?:
100% reproducible when an invalid or unreachable NFS installation source is provide
Steps to reproduce
- Create a Kickstart file with an NFS or any installation source .
- Boot the system using Anaconda installer with this Kickstart file.
- Ensure the NFS server is unreachable or the path is incorrect.
- Proceed with the installation.
Expected results
The installer should display a clear error message indicating that the NFS installation source cannot be reached and stop the installation process.
Actual results
No error is shown in the UI. The failure is only logged in /tmp/packaging.log, and the installer enters an infinite loop at “Checking storage configuration.”

- duplicates
-
RHEL-60724 anaconda hangs on 'Checking Storage Config' when faulty repository is used in kickstart
-
- Release Pending
-