Bug 1143864
| Summary: | unable to do manual partitioning | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||||||||
| Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 21 | CC: | anaconda-maint-list, awilliam, collura, g.kaviyarasu, jonathan, kparal, lnie, robatino, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | AcceptedBlocker | ||||||||||||
| Fixed In Version: | python-blivet-0.61.3-1 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2014-10-15 21:10:12 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: | 1043124 | ||||||||||||
| Attachments: |
|
||||||||||||
Please attach the logs from /tmp: anaconda.log storage.log program.log Don't make an archive -- attach them one at a time, please. Thanks. Created attachment 939897 [details]
anaconda.log
Created attachment 939898 [details]
program.log
Created attachment 939899 [details]
storage.log
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. 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/ 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! Sure,my pleasure. Tested the 21 Beta TC2 just now,and the bug seems gone. 0.61.3 went stable, so let's close. Thanks for the confirmation, lili! |
Created attachment 938769 [details] screenshot 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): f21-RC1(x86_64) How reproducible: 100% 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: