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.
Formatting DASDs works correctly during a text-based installation
Previously, a bug prevented DASDs from being correctly formatted during a text-based installaton. As a consequence, DASDs that were unformatted or incorrectly formatted had to be manually formatted before use. This bug has been fixed, and the installer can now format DASDs when performing a text-based installation.
Description of problem:
The installer doesn't format unformatted DASD disks (formatted by cpfmtxa in CMS) when running a kickstart installation in text mode. Those disks are ignored during the installation.
Version-Release number of selected component (if applicable):
RHEL-7.0 GA
RHEL-7.1 GA
RHEL-7.2 Beta (anaconda-21.48.22.35-1.el7)
How reproducible:
always
Steps to Reproduce:
1. format a DASD disk in CMS using the "cpfmtxa" command
2. run a kickstart installation in text mode with the following commands in the kickstart file:
bootloader --location=mbr
zerombr
clearpart --all --initlabel
autopart
Actual results:
Unformatted DASD disk not formatted using dasdfmt during the installation
Expected results:
Unformatted DASD disk are formatted and used during the installation
Not only unformatted, but also LDL disks are not formatted during kickstart installation in text mode when having the following line in the kickstart file:
clearpart --all --initlabel --cdl
Since I believe the root cause is the same, I'm using this bug for LDL disks as well. In case the root case is different, I will report a new bug.
Retested with anaconda-21.48.22.70-1.el7, but the unformatted DASD wasn't formatted during the installation. After the installation:
[root@rtt7 ~]# lsdasd
Bus-ID Status Name Device Type BlkSz Size Blocks
==============================================================================
0.0.3127 active dasda 94:0 ECKD 4096 2347MB 601020
0.0.3227 active dasdb 94:4 ECKD 4096 2347MB 601020
0.0.3027 n/f dasdc 94:8 ECKD
[root@rtt7 ~]#
Moving back to ASSIGNED.
Retested with anaconda-21.48.22.79-1.el7 - LDL DASD isn't formatted with CDL during kickstart installation in text mode (ks installation in vnc mode works fine).
Partitioning part of the kickstart file:
bootloader --location=mbr
zerombr
clearpart --all --initlabel --cdl
autopart
Installation logs will be attached, moving to ASSIGNED.
Retested with anaconda-21.48.22.86-1.el7 and this issue is fixed, both unformatted and LDL formatted DASD disks are formatted with CDL in text mode.
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.
https://rhn.redhat.com/errata/RHEA-2016-2158.html