Bug 1636525

Summary:	Anaconda uses LDL DASD disks during kickstart installations
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Stodola <jstodola>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.6	CC:	jkonecny
Target Milestone:	rc
Target Release:	---
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-15 07:43:18 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:	1568427, 1670353

Description Jan Stodola 2018-10-05 15:18:27 UTC

Description of problem:
Anaconda doesn't stop when running a kickstart installation on a system with an LDL DASD disk.
Since LDL disks are not supported during installation, anaconda should not use them and let the user to proceed through the storage spoke manually (in case of vnc/text installation), or stop the installation in case of cmdline UI mode.

Version-Release number of selected component (if applicable):
RHEL-7.6
anaconda-21.48.22.147-1.el7
python-blivet-0.61.15.72-1.el7

How reproducible:
always

Steps to Reproduce:
1. format one DASD with LDL (dasdfmt -d ldl -b 4096 /dev/dasdX)
2. run a kickstart installation, use the LDL disk and the following partitioning section:

bootloader --location=mbr
zerombr
clearpart --all --initlabel
autopart


Actual results:
anaconda used the LDL DASD during the installation

Expected results:
anaconda should stop (in cmdline UI mode), or allow the user to go through the storage spoke manually (in vnc/text UI mode).

Comment 9 RHEL Program Management 2021-02-15 07:43:18 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.