Bug 889520
| Summary: | anaconda does not reject a storage configuration (automatic partitioning reclaimed space but it is not contiguous and spans disks with different disk-label) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Reartes Guillermo <rtguille> | ||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 18 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2014-02-05 14:05: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: | |||||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 667270 [details]
program.log
Created attachment 667271 [details]
storage.log
Created attachment 667272 [details]
vda partition table
Created attachment 667273 [details]
vdb partiton table
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 667269 [details] anaconda.log Description of problem: In this case, anaconda does not know what to do when ones gets enough space, but spread across two disks with different disk-labels. Version-Release number of selected component (if applicable): anaconda 18.37.5 (smoke9) How reproducible: always Steps to Reproduce: Do this first: * disk#1 as a previous F18 instance (BTRFS Automatic Partitioning) (MSDOS Disklabel) * disk#2 as a previous F18 instance (BTRFS Automatic Partitioning) )GPT Disk-label) 0. Boot (no kernel parameters) anaconda 18.37.5 (smoke9) 1. Select KDE in SOFTWARE SELECTION 2. Enter STORAGE: INSTALLATION DESTINATION 3. Select both vda and vdb, go to 'reclaim space' 4. Set 'delete' to the two SWAP (one per disk) to reach the required space 5. In the main hub "automatic partitioning selected' is show. 6. But a YELLOW BANNER in the MAIN HUB says: "not enough space in file-systems..." Additionally: 7. Enter STORAGE: INSTALLATION DESTINATION (AGAIN) 8. Select both vda and vdb, go to 'reclaim space' 9. No SWAP entries are shown. That is bad. 10. 'cancel' is the only option. Actual results: an additional issue, steps #7 and later. Expected results: reject storage configuration or be able to use these reclaimed space. Additional info: