Bug 158696
| Summary: | Anaconda/Disk Druid displays wrong size for LVM VG member in VG dialog. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul W. Frields <stickster> |
| Component: | anaconda | Assignee: | Chris Lumens <clumens> |
| Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-08-15 16:52:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Chris -- can you take a look at this? If the fix is simple enough, it'd be good to get into FC4 although it is late :/ Committed a fix to head and fc4-branch. |
Description of problem: I noticed this problem while making screenshots for the upcoming Fedora Installation Guide. It is not a showstopper, but is misleading and possibly confusing to users. This seems to happen when a disk has pre-existing LVM partitions. Version-Release number of selected component (if applicable): 10.2.0.61-1 How reproducible: Every time, AFAICT. Steps to Reproduce: 1. Start with a disk with a pre-existing LVM setup. My guest OS has a 40 GB disk ("sda") available, that had a ~100 MB /boot partition (ext3), a ~3200 MB LVM partition/PV, and a ~300 MB swap partition. 2. Boot FC4t3 anaconda and manually partition disk. 3. Remove existing partitions and create new ones: ~100 MB fixed /boot (ext3, sda1), ~40 GB LVM PV (sda2). 4. Select "LVM" button to enter "Make LVM Volume Group" dialog. Actual results: Size of VG member sda2 is displayed as 3200 MB, which is incorrect. Expected results: Size of sda2 should be ~40000 MB. Additional info: I am using VMware but would not expect different behavior from a "real" machine (which I don't have available to test). Because this is not a showstopper bug, I wouldn't expect it to be fixed for FC4 final, but I will be happy to test the bug with the final release on a "real" machine. Unfortunately, I have none available at present, but will in June.