Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1148930 - kickstart lvm partitioning fails
Summary: kickstart lvm partitioning fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python-blivet
Version: 21
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F21BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2014-10-02 16:37 UTC by Orion Poplawski
Modified: 2014-10-02 17:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-02 17:29:50 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
storage.log (93.18 KB, text/plain)
2014-10-02 16:37 UTC, Orion Poplawski 		no flags Details
storage.state (28.00 KB, text/plain)
2014-10-02 16:38 UTC, Orion Poplawski 		no flags Details
View All

Description Orion Poplawski 2014-10-02 16:37:10 UTC 
Created attachment 943488 [details]
storage.log

Description of problem:

Trying to do kickstart install of F21 Beta TC1 with following partitioning:

clearpart --linux --drives=sda
part /boot --size=200 --ondisk=sda
part pv.1 --size 48000 --ondisk=sda --grow
volgroup vg_root pv.1
logvol / --vgname=vg_root --size=3500 --name=root
logvol swap --fstype=swap --vgname=vg_root --recommended --name=swap
logvol /var --vgname=vg_root --size=2000 --name=var
logvol /var/crash --vgname=vg_root --size=20000 --name=crash
zerombr
bootloader --location=mbr

I get a message of no disks selected and am dumped into the configuration screen.  Manual config fails as well.
Comment 1 Orion Poplawski 2014-10-02 16:38:38 UTC 
Created attachment 943489 [details]
storage.state
Comment 2 David Lehman 2014-10-02 17:08:17 UTC 
clearpart --type=linux doesn't clear partitions based only on partition type code. If the partition actually contained swap space it would have been cleared. The result is that you have no free space to allocate new partitions from.
Comment 3 Orion Poplawski 2014-10-02 17:29:50 UTC 
Ah, sorry about that.  Clearing the partition manually allows the install to proceed.
Note You need to log in before you can comment on or make changes to this bug.