Bug 232511
| Summary: | Anaconda dies with its own generated kickstart file | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Juan Quintela <quintela> | ||||||
| Component: | anaconda | Assignee: | Peter Jones <pjones> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | rawhide | CC: | mattdm, quintela, triage | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | bzcl34nup | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2008-05-07 01:17: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: |
|
||||||||
Created attachment 150168 [details]
my kickstart file
Created attachment 150169 [details]
anaconda stack trace
Fedora 7 test bugs should be filed against "devel", not against test1/2/3. This isn't obvious, I know. Moving this report so it isn't lost. This is a bulk message -- I apologize if this was actually meant to be targeted against a different release. If so, please fix or let me know. Thanks. Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp |
Description of problem: Using the anaconda-ks.cfg generated file by anaconda install launchs one exception. Problem is the partitioning code. part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 --pesize=32768 pv.2 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=352 --grow --maxsize=704 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow I have tried with values of --size={10,100,1500} as suggested by clummens. It produces the same problem. Version-Release number of selected component (if applicable): Fedora Rawhide How reproducible: It happens always Steps to Reproduce: 1. Try to install using a kickstart file form a previous installation. I am attaching mine. 2. Install using the kickstart file. Actual results: Python stack trace during install. Expected results: Kickstart working and partitioning the disk correctly. Notice that this configuration has worked for FC5/FC6/RHEL5. And it is the hint that anaconda itself gives (still in current rawhide). Additional info: That values are the ones that anaconda generates when I select it to autopartition my disk (it is a 4GB disk). There is no better way (that I know) of generating it.