Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Assigning mount points to existing block devices is now possible in Kickstart installations
A new "mount" command is now available in Kickstart. This command assigns a mount point to a particular block device with a file system, and it can also reformat it if you specify the "--reformat" option.
The difference between "mount" and other storage-related commands like "autopart", "part", or "logvol" is that with "mount" you do not need to describe the entire storage configuration in the Kickstart file, you only need to make sure that the specified block devices exist on the system. However, if you want to create the storage configuration instead of using an existing one, and mount the various devices, then you must use the other storage configuration commands.
You can not use "mount" with the other storage configuration commands in the same Kickstart file.
Description of problem:
Is is impossible to do manual partitioning during text installation. It is even impossible to use *existed partitions* to map mount-points.
During server installation I often use text installation (it is light enough. I do not need extra VNC/graphic for that, especially on IBM Power). But I need to create custom disk partitioning, without /home, with hard raid or lvm, next to other OS and so on. It would be strongly cool, if anaconda has a screens like
> custom disk partitioning
>> map mountpoints to existed partitions (and note, that user can use tty2 for custom partitioning)
>> run custom partitioning (run shell, or fdisk/parted) and then map
Version-Release number of selected component (if applicable):
anaconda-21.48.22.113 (or even rhel7-branch on GitHub)
How reproducible:
always
Steps to Reproduce:
1. run installation in text mode
2. try to create custom partitions in interactive way
3. or try to reuse existed partitions
Actual results:
there is no way for that (only automatic partitioning)
Expected results:
there is way to do that.
Comment 2Vratislav Podzimek
2017-05-15 14:01:05 UTC
Let's make the bug summary more precise.
Comment 3Samantha N. Bueno
2017-10-23 10:40:36 UTC
Backporting the work from Fedora to RHEL is non-trivial since it involves basically rewriting the patches. That's too invasive for this release, so the scope of this has been limited to kickstart support as far as 7.5 is concerned.
Comment 4Vratislav Podzimek
2017-10-23 14:31:18 UTC
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.
https://access.redhat.com/errata/RHBA-2018:0671
Description of problem: Is is impossible to do manual partitioning during text installation. It is even impossible to use *existed partitions* to map mount-points. During server installation I often use text installation (it is light enough. I do not need extra VNC/graphic for that, especially on IBM Power). But I need to create custom disk partitioning, without /home, with hard raid or lvm, next to other OS and so on. It would be strongly cool, if anaconda has a screens like > custom disk partitioning >> map mountpoints to existed partitions (and note, that user can use tty2 for custom partitioning) >> run custom partitioning (run shell, or fdisk/parted) and then map Version-Release number of selected component (if applicable): anaconda-21.48.22.113 (or even rhel7-branch on GitHub) How reproducible: always Steps to Reproduce: 1. run installation in text mode 2. try to create custom partitions in interactive way 3. or try to reuse existed partitions Actual results: there is no way for that (only automatic partitioning) Expected results: there is way to do that.