Bug 581218
Summary: | partition config in interactive kickstart results in extra LVM VolGroup | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Larry O'Leary <larryoleary> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | anaconda-maint-list, fedora, jonathan, lgillesp, vanmeeuwen+fedora |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-09-09 13:36:46 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: | |||
Attachments: |
Description
Larry O'Leary
2010-04-11 07:23:12 UTC
This sounds very familiar to me, though I'm not able to find a specific commit or bug report offhand. I know we've had interactive kickstart partitioning bugs before and I know I've fixed several. Can you please give F13 a quick test with the same setup and verify whether or not you're still seeing this problem? If you are, I'll take a look at it again. Thanks. Can you reproduce the bug on F13, Larry? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Sorry for the delay... Attempting my previous test now fails during interactive configuration. I am asked what storage layout I would like to us but I simply click next (leaving the default of Use entire disk). Next, I get the following error: Could not allocate requested partitions: not enough space for LVM requests. Press 'OK' to exit the installer. The installation will not proceed. I also tried checking the "View/Modify Layout" checkbox in the hopes that I could see what was actually going on but to no avail. The disk size in 80GB so it should be sufficient to hold the partition information in the Kickstart file. Additionally, the partition configuration specifies minimum and maximum sizes that I would expect to fit on even a 30GB disk. Thoughts? Created attachment 443029 [details]
Anaconda error when attempting to use "All Space" option with pv.01 set to --size=1 --grow
Created attachment 443030 [details]
Anaconda error after Finding Storage Devices... with no --size for pv.01
Also re-tested using 160GB disk with same result. I then re-tested using the 160GB disk but this time I selected the "Create Custom Layout" option. I could now see my disk layout, however all the minimum sizes were used (in other words, they did not grow to the --maxsize setting). Additionally, when I clicked on one of the partitions (lv_root for example) an uncaught exception occurred (anaconda-exception-001.txt) and the installer terminated. I believe the uncaught exception was due to the vg_default Volume Group having a size of 0 while the Logical Volumes had sizes greater than 0. It appears that the --grow argument was ignored for part pv.01 which is where vg_default was being placed. I then reattempted the install with an updated layout in the Kickstart file of: clearpart --all --drives=sda part /boot --fstype=ext4 --size=200 part pv.01 --grow volgroup vg_default --pesize=4096 pv.01 logvol / --fstype=ext4 --name=lv_root --vgname=vg_default --grow --maxsize=10240 logvol swap --name=lv_swap --vgname=vg_default --recommended logvol /var --fstype=ext4 --name=lv_var --vgname=vg_default --grow --maxsize=5120 logvol /home --fstype=ext4 --name=lv_home --vgname=vg_default --grow --maxsize=40960 logvol /tmp --fstype=ext4 --name=lv_tmp --vgname=vg_default --grow --maxsize=6144 logvol /opt --fstype=ext4 --name=lv_opt --vgname=vg_default --grow --maxsize=10240 Essentially, all the size options have been removed in the hope to cause maxsize and grow to work. But still no success. Now, Anaconda fails shortly after the GUI is started -- after the Finding Storage Devices message -- with an uncaught exception (anaconda-exception-002.txt). From the looks of the debug log, size is required for the part command in the Kickstart file. I even tried to simply use the --recommended option for the part but same error. --size seems to be required. So, I gave up on the idea that Kickstart and Anaconda could be smart enough to figure out what I am really wanting. So, I have now hard-coded the --size for part and all logvol: clearpart --all --drives=sda --initlabel part /boot --fstype=ext4 --size=200 part pv.01 --grow --size=9216 volgroup vg_default --pesize=4096 pv.01 logvol / --fstype=ext4 --name=lv_root --vgname=vg_default --size=1024 --grow --maxsize=10240 logvol swap --name=lv_swap --vgname=vg_default --recommended logvol /var --fstype=ext4 --name=lv_var --vgname=vg_default --size=1024 --grow --maxsize=5120 logvol /home --fstype=ext4 --name=lv_home --vgname=vg_default --size=5120 --grow --maxsize=40960 logvol /tmp --fstype=ext4 --name=lv_tmp --vgname=vg_default --size=1024 --grow --maxsize=6144 logvol /opt --fstype=ext4 --name=lv_opt --vgname=vg_default --size=1024 --grow --maxsize=10240 But, this has still not given me what I need. It does seem to prevent the uncaught exceptions from occurring but I can see the vg_default is actually still too large to fit onto pv.01. Furthermore, pv.01 (sda2) doesn't show up under the Hard Drives list for sda. The only thing I see there is a bunch of unallocated space. However, it gets even stranger. Clicking Create on the unallocated space and setting it to LVM and "all available space" creates a third partion sda3 which suddenly results in sda1, sda2, and sda3 showing up under Hard Drives. Furthermore, vg_default on pv.01 has now grown to all available space. Of course, the Logical Volumes are still very tiny. I then re-attempted my original test with the new partition layout in my Kickstart file. This was to simply select the "Use All Space" option rather then the "Create Custom Layout" option. I also checked the View/Modify checkbox so I could see the layout. And I am now seeing the same thing I saw in Fedora 12. The default layout is used VolGroup -- lv_root and lv_swap and then my layout appears on sda5 with vg_default and my lvs. So, it would seem at the moment, that one can get around these strange glitches by simply selecting the "Create Custom Layout" and then tweaking the settings from the Kickstart file but this does defeat the purpose of providing a default layout/setup that a user might want to tweak. I could get around the hard-coding by using post-install scripts and includes to dynamically build the partition layout based on the machine but it would be nice for this simple use case to work. Interactive kickstart installs have been deprecated, given this and other similar difficulties. Note that this only applies to use of the "interactive" command. Omitting information from a kickstart file will still cause anaconda to stop and prompt for it. |