Bug 499225
| Summary: | F11 Preview: Kickstart install crashes when installing over an encrypted partition | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ajs <ajsfedora> | ||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 11 | CC: | anaconda-maint-list, pjones, rmaximo, vanmeeuwen+fedora | ||||||
| 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: | 2009-09-04 17:44:20 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: |
|
||||||||
In the 'Steps to Reproduce:' section, add 6. Enter password for encrypted partition Also, adding %traceback umount /dev/sdb1 mount -o rw /dev/sdb1 /tmp/mnt cp /tmp/anacdump.txt /tmp/mnt does not result in anacdump.txt being copied to the USB stick Created attachment 342496 [details]
Photo of the traceback
Here is a picture of the traceback sing the %traceback script is not working for me
While I filled out this report by installing F11 preview and used the generated kickstart file, I did this to make sure that there were not changes in the kickstart syntax that I was unaware of. The error first showed up when I tried to reinstall over an F10 installation. This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This looks like a legitimate bug, but we could really use the anacdump.txt file to figure out what request.path looks like. Can you add some debugging to figure out what might be going wrong with the %traceback script and attach the file if at all possible? I assume that you want me to try with the released version of F11. I will download it now. That'd be great, thanks. I'm in the middle of a design review: I have not forgotten. I tried once and got a different error and will look at it when I have a few minutes of time. |
Created attachment 342491 [details] Kickstart file that causes a ValueError to be raised Description of problem: When doing a kickstart install on an encrypted partition, kickstart raises a ValueError exception with the message "device must be a fully qualified path" Version-Release number of selected component (if applicable): 11.5.0.47 How reproducible: Always Steps to Reproduce: 1. Install F11-Preview and encrypt the root partition 2. Edit the generated anaconda-ks.cfg, adding partitioning commands # == Partitions clearpart --linux --drives=sda part /boot --fstype ext3 --size=200 --ondisk=sda part pv.41 --encrypted --size=0 --grow --ondisk=sda --passphrase="test" volgroup vg_fleuret --pesize=32768 pv.41 logvol / --fstype ext4 --name=lv_root --vgname=vg_fleuret --size=1024 --grow logvol swap --fstype swap --name=lv_swap --vgname=vg_fleuret --size=1936 --grow --maxsize=3872 3. Copy the anaconda-ks.cfg to a USB stick (see attachment) 4. Reboot from the install CD 5. Edit the boot arguments, adding e.g. 'ks=hd:sdb1/anaconda-ks.cfg' Actual results: ValueError exception with the message "device must be a fully qualified path" Expected results: Successful installation Additional info: