Bug 1143864 - unable to do manual partitioning
Summary: unable to do manual partitioning
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 21
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F21BetaBlocker
TreeView+ depends on / blocked
Reported: 2014-09-18 07:37 UTC by lnie
Modified: 2014-10-15 21:10 UTC (History)
9 users (show)

Fixed In Version: python-blivet-0.61.3-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-10-15 21:10:12 UTC
Type: Bug

Attachments (Terms of Use)
screenshot (80.73 KB, application/octet-stream)
2014-09-18 07:37 UTC, lnie
no flags Details
anaconda.log (14.83 KB, text/plain)
2014-09-22 06:51 UTC, lnie
no flags Details
program.log (13.16 KB, text/plain)
2014-09-22 06:52 UTC, lnie
no flags Details
storage.log (42.51 KB, text/plain)
2014-09-22 06:52 UTC, lnie
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1121383 0 unspecified CLOSED ValueError: specified lv is not part of this vg 2021-02-22 00:41:40 UTC

Internal Links: 1121383

Description lnie 2014-09-18 07:37:13 UTC
Created attachment 938769 [details]

Description of problem:

As shown in the screenshot,anaconda keeps saying "No disks specified for the new device",even though ,actually,the disks is chosen by default in the INSTALLATION DESTINATION page

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Do a default install 
2.choose "I will configure partitioning" option in the INSTALLATION DESTINATION page
3.try to do custom partitiong in the manual partitiong page,
like add a new mount point
4.then you will see the warning 

Actual results:

Expected results:

Additional info:

Comment 1 David Lehman 2014-09-19 17:33:49 UTC
Please attach the logs from /tmp:


Don't make an archive -- attach them one at a time, please. Thanks.

Comment 2 lnie 2014-09-22 06:51:37 UTC
Created attachment 939897 [details]

Comment 3 lnie 2014-09-22 06:52:05 UTC
Created attachment 939898 [details]

Comment 4 lnie 2014-09-22 06:52:55 UTC
Created attachment 939899 [details]

Comment 5 David Lehman 2014-09-22 14:25:12 UTC
I'm surprised this is the first report of this bug. We schedule actions to initialize the disk. Then, upon entering the custom spoke, we hide the zRAM device, which has the side-effect of canceling all scheduled actions, leaving the disk uninitialized and therefore unusable. (Nothing is actually being done to your disk -- this is all in the installer's in-memory model.)

This is fixed on master for seemingly different bug 1121383.

Comment 6 Kamil Páral 2014-09-24 17:51:26 UTC
Discussed in 2014-09-24 Blocker Review meeting [1]. Accepted as a blocker. This bug violates the Beta Custom partitioning criteria: "Correctly interpret, and modify as described below, any disk with a valid ms-dos or gpt disk label and partition table containing ext4 partitions, LVM and/or btrfs volumes, and/or software RAID..."

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-09-24/

Comment 7 Adam Williamson 2014-10-08 16:44:06 UTC
Discussed at 2014-10-08 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-08/f21-blocker-review.2014-10-08-15.58.log.txt . Should be fixed in 21 Beta TC2, if the fix is in python-blivet 0.61.3-1. lili, can you please test? Thanks!

Comment 8 lnie 2014-10-09 03:17:00 UTC
Sure,my pleasure.
Tested the 21 Beta TC2 just now,and the bug seems gone.

Comment 9 Adam Williamson 2014-10-15 21:10:12 UTC
0.61.3 went stable, so let's close. Thanks for the confirmation, lili!

Note You need to log in before you can comment on or make changes to this bug.