Red Hat Bugzilla – Bug 1261153
[RFE] Add a mechanism to validate pre-reqs are satisfied before proceeding with install.
Last modified: 2017-02-27 09:42:21 EST
Description of problem:
This RFE came about when an install was performed on a host with only 8GB of memory. The install proceeded and errors were seen during content synchronization. The errors were likely the result of running with not enough memory available.
The minimal requirements are 12GB which is covered in documentation.
To help a user understand this and avoid a bad experience we'd like to enforce a check for pre-reqs when the ISO is running, in case they missed reading the minimal reqs in the docs.
Ideally we could execute a script to check:
- RAM is sufficient
- Hard Drive space is sufficient
Thinking is this would be part of the ISO installer, so it'd be integrated with anaconda. If that proves too difficult we could add a warning in fusor-installer when first run.
After some discussion with John Matthews, putting the requirement-check-script in fusor-installer and fusor-undercloud-installer rather than Anaconda seem to be the correct solution for now so that the ISO build process is not complicated.
Made changes to fusor-installer and fusor-undercloud-installer to implement RFE.
fusor-installer PR: https://github.com/fusor/fusor-installer/pull/80
fusor-undercloud-installer PR: https://github.com/fusor/fusor-undercloud-installer/pull/43
Bringing this back to MODIFIED so that it can be brought into the compose.
Joseph Magen reported an issue with the RAM check detecting 0MB.
I switched the check over to "free -m" instead of "dmidecode -t 17" to prevent similar problems in the future.
Will be in compose 8/5
Verified with QCI-1.0-RHEL-7-20160806.t.0
- installing with 8Gb of RAM.
- installing with 2 cores.
- installing with 1 core.
- installing with too little disk storage.
All scenarios passed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.