Bug 864708

Summary:	Handle autopart for s390x
Product:	[Fedora] Fedora	Reporter:	Jesse Keating <jkeating>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	anaconda-maint-list, awilliam, dcantrell, g.kaviyarasu, jonathan, jstodola, mbanas, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-18.17-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-23 03:28:54 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:

Description Jesse Keating 2012-10-09 23:33:21 UTC

s390x makes use of many small dasd devices.  Right now it's impossible to use the autopart option as the devices are all too small for any individual one to hold a big enough root filesystem.  LVM must be used.  Having to manually select and create 14~ LVM partitions, then the filesystems on top of them is really really tedious.  (thankfully I could just re-use the existing partitions now).

I don't think a "use lvm" switch is coming for F18, perhaps we can detect s390x platform and default to lvm for the autopart?

Comment 1 Chris Lumens 2012-10-11 02:46:01 UTC

dlehman has an interesting idea for this involving falling back to AUTOPART_TYPE_LVM should AUTOPART_TYPE_PLAIN (or NONE, or whatever it's called) fail.  That would fix this up, I think.

Comment 2 Jesse Keating 2012-10-11 04:51:54 UTC

I think that would fix it up nicely, and avoid more "if s390" crap.

Comment 3 Chris Lumens 2012-10-12 16:54:42 UTC

fbc7589a05c773824888c7e74dfc3826715ec432

Comment 4 Fedora Update System 2012-10-17 03:08:25 UTC

anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18

Comment 5 Fedora Update System 2012-10-17 17:29:48 UTC

Package anaconda-18.17-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.17-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16295/anaconda-18.17-1.fc18
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2012-10-18 02:37:24 UTC

anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18

Comment 7 Fedora Update System 2012-10-18 15:29:34 UTC

Package anaconda-18.18-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.18-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16402/anaconda-18.18-1.fc18
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2012-10-20 01:33:08 UTC

anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18

Comment 9 Adam Williamson 2012-11-23 03:28:54 UTC

This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.