Bug 868671
| Summary: | F18b TC6 anaconda does not count certain disks as having free space and trying to create partitions on those results in "KeyError: '/dev/sda'" | ||
|---|---|---|---|
| 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, 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 12:39:29 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: | |||
|
Description
Reartes Guillermo
2012-10-21 15:18:44 UTC
Created attachment 630913 [details]
manual partitioning showing the abnormal condition of some disks
Created attachment 630914 [details]
manual partitioning showing the abnormal condition of some disks #2
Created attachment 630916 [details]
manual partitioning showing the abnormal condition of some disks #3
Created attachment 630917 [details]
manual partitioning showing the abnormal condition of some disks #3
Anaconda, for some reason thinks that i can reclaim space on an unpartitioned disk. :-)
There was an additional disks (the first one) and was IDE (sda) and was partitioned, i switched it to virtio and became the last. Sadly, it does not fix the issue. This is the previous SDA (now VDA) disk partition table: GPT fdisk (gdisk) version 0.8.4 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format. *************************************************************** Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/vdg: 22528000 sectors, 10.7 GiB Logical sector size: 512 bytes Disk identifier (GUID): C47AD18A-EE9E-42A1-86AE-3EF063961A2E Partition table holds up to 128 entries First usable sector is 34, last usable sector is 22527966 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 1026047 500.0 MiB 8300 Linux filesystem 2 1026048 2598911 768.0 MiB 8200 Linux swap 3 2598912 22527999 9.5 GiB 8300 Linux filesystem Are you still seeing this problem with one of the F18 final test trees? Created attachment 671555 [details]
screenshot showing the issue on smoke12
Yes, it does still happen with smoke12.
I zapped all disks and then booted smoke12, and anaconda showed the same issue when selecting these disks.
Created attachment 671556 [details]
smoke12 storage.log
Created attachment 671558 [details]
smoke12 anaconda.log
Created attachment 671561 [details]
smoke12 program.log
Created attachment 671566 [details]
screenshot showing btrfs volumes being detected on unpartitioned devices
As the screen-shot shows, btrfs volumes are being detected even with an un-partitioned disk. (blkid also detect something on the disks, so they are not empty).
While i did zap the disks, i did not perform a 'dd' to the first megabyte of the disks just to be sure.
It appears that, while unintended, these disks were left as a whole-device by accident and anaconda cannot perform any actions to these disks.
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. |