Bug 887609
| Summary: | anaconda shows a 'biosboot' or a 'prepboot' in both the 'unknown' and 'new feodora..' trees if they are the only partition | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Reartes Guillermo <rtguille> | ||||||||||
| Component: | anaconda | Assignee: | Brian Lane <bcl> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | rawhide | CC: | 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-10-07 22:26:52 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 664464 [details]
storage.log
Created attachment 664465 [details]
program.log
Created attachment 664466 [details]
X.log
If you remove a device from any tree other than the "New Fedora..." tree it will actually be removed from the disk, hence the warning. Removing it from the "New Fedora..." tree means "revert it to its original state if it exists, otherwise cancel its pending creation." This is probably confusing, but if you think about it this behavior makes a great deal of sense. |
Created attachment 664463 [details] anaconda.log Description of problem: If one creates a 'biosboot' or a 'prepboot' partition, and 'finish partitioning', when returning to manual partitioning one will find the partition shown in two trees at once. Worse, deleting it from the 'unknown' gets anaconda stuck. Version-Release number of selected component (if applicable): F18 TC2 (18.37.2) How reproducible: always Steps to Reproduce: 0. boot anaconda (in this example, it was booted with 'gpt' and partitions but the disk has a gpt disk label) 1. go to manual partitioning, and create either a 1mb 'biosboot' or a 10mb 'prepboot' and 'finish partitioning 2. in the main hub, the storage configuration is rejected (that is ok) 3. go to manual partitioning (again) 4. by default the 'unknown' tree is expanded with the created partition 5. expanding the 'new fedora' shows the same partition 6. deleting it from the 'unknown' tree (SOMETIMES) causes anaconda to get stuck (and hit 867770) Actual results: biosboot and prepboot are shown in two trees at the same time. Expected results: only show the partition in one tree. Additional info: Sometimes i can delete the partition and it disappears from both trees.