The "reqpart" Kickstart command will now only create partitions that are required by the hardware platform
Previously, when the "reqpart" command was specified in a Kickstart file and no partitions were required by the hardware platform, the installer attempted to perform automatic partitioning.
As a result, the installation failed with an error.
This update ensures that the "reqpart" Kickstart command will only create partitions that are required by the hardware platform.
Description of problem:
When running kickstart installation on s390x and reqpart is specified in the ks file, anaconda fails to create requested partition scheme. The partitioning part of the ks file:
clearpart --all --initlabel
part / --size=4000
part swap --fstype=swap --size=1000
Version-Release number of selected component (if applicable):
RHEL-7.5 / s390x
always on s390x
Steps to Reproduce:
1. run kickstart installation with the partitioning defined above
[ 45.627288] anaconda: Starting installer, one moment...
[ 45.627577] anaconda: anaconda 188.8.131.52-1 for Red Hat Enterprise Li
nux 7.5 started.
[ 45.627765] anaconda: * installation log files are stored in /tmp durin
g the installation
[ 45.627952] anaconda: * when reporting a bug add logs from /tmp as sepa
rate text/plain attachments
[ 45.628145] anaconda: 16:02:13 Not asking for VNC because of an automat
[ 45.628996] anaconda: 16:02:13 Not asking for VNC because text mode was
explicitly asked for in kickstart
[ 58.103369] anaconda: Starting automated install.......
[ 58.103813] anaconda: Checking software selection
[ 58.104001] anaconda: Generating updated storage configuration
[ 58.104189] anaconda: storage configuration failed: Unable to allocate
requested partition scheme.
Successful installation. No other partition is created by reqpart, since it's not needed on s390x.
Created attachment 1408925 [details]
Created attachment 1408926 [details]
Created attachment 1408928 [details]
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/1424
Verified with anaconda-184.108.40.206-2.el7 using the steps from the bug description and this bug is fixed.
Thanks, moving to VERIFIED.
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.