Bug 1269174

Summary: Unable to identify DASD devices before formatting them with dasdfmt
Product: Red Hat Enterprise Linux 7 Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: Vendula Poncova <vponcova>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact: Petr Bokoc <pbokoc>
Priority: medium    
Version: 7.2CC: herrold, pbokoc, sbueno
Target Milestone: rc   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-21.48.22.122-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 08:45:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1256306, 1478303    
Attachments:
Description Flags
screenshot
none
storage.log none

Description Jan Stodola 2015-10-06 14:07:26 UTC 
Description of problem:
When anaconda asks to format unformatted or LDL DASD disks, it is not clear which DASD disks will be formatted. Anaconda only shows device names (for example /dev/dasdh), which are not persistent and changes across reboots. Anaconda should show the DASD device ID of the disks to be formatted.
This needs to be fixed in both GUI and TUI mode.

Version-Release number of selected component (if applicable):
RHEL-7.1 GA
RHEL-7.2 Snap4 (anaconda-21.48.22.53-1.el7)

How reproducible:
always

Steps to Reproduce:
1. format one or more DASD disks using cpfmtxa in CMS
2. start the installation
3. select all disks
4. let anaconda create the partitions
5. review the list of disks to be formatted using dasdfmt

Actual results:
unable to identify what DASD disks will be formatted

Expected results:
able to identify what DASD disks will be formatted - anaconda should show the device ID in any form, for example "0.0.3024"

Work around:
Log in via ssh during the installation and run "lsdasd" to match device names and device IDs.
Comment 1 Jan Stodola 2015-10-06 14:08:09 UTC 
Created attachment 1080245 [details]
screenshot
Comment 4 Jan Stodola 2015-10-06 14:15:18 UTC 
Created attachment 1080254 [details]
storage.log
Comment 8 Jan Stodola 2016-07-18 09:25:16 UTC 
Device IDs are shown in GUI installation, but not in TUI installation:

The following unformatted or LDL DASDs have been detected on your system. You
can choose to format them now with dasdfmt or cancel to leave them unformatted.
Unformatted DASDs cannot be used during installation.

/dev/dasde
/dev/dasdd
Warning: All storage changes made using the installer will be lost when you
choose to format.

Tested with anaconda-21.48.22.79-1.el7, moving back to ASSIGNED.
Comment 9 Samantha N. Bueno 2016-08-26 16:59:04 UTC 
This is actually not going to be simple to fix -- at least, not simple (non-invasive) enough for 7.3 at this point. So I'm going to defer it until 7.4.
Comment 12 Vendula Poncova 2017-08-14 08:44:59 UTC 
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/1147
Comment 14 Jan Stodola 2017-12-05 12:02:21 UTC 
This is fixed and anaconda shows the IDs of the disks before running dasdfmt in text UI:

The following unformatted or LDL DASDs have been detected on your system. You
can choose to format them now with dasdfmt or cancel to leave them unformatted.
Unformatted DASDs cannot be used during installation.

/dev/dasdf (0.0.3126)
/dev/dasdb (0.0.3026)

Warning: All storage changes made using the installer will be lost when you
choose to format.

Proceed to run dasdfmt?


Verified with anaconda-21.48.22.128-1.el7.
Comment 18 errata-xmlrpc 2018-04-10 08:45:01 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