Bug 873445
Summary: | Changing encryption state in custom partitioning can lead to failure/crash | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
Component: | anaconda | Assignee: | David Lehman <dlehman> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | anaconda-maint-list, g.kaviyarasu, johannbg, jonathan, tflink, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | AcceptedNTH | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-11-08 09:42:06 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: | |||
Bug Depends On: | |||
Bug Blocks: | 752664 |
Description
Adam Williamson
2012-11-05 21:25:18 UTC
oh, forgot to mention - dlehman says the fix for this is not complicated, and he has been testing it. +1 nth I'm +1 NTH for a tested fix, I imagine that a lot of people would hit this bug and it's not fixable with an update. +1 NTH that's 4 +1s, marking accepted NTH. thanks for the votes everyone. Updates image: http://dlehman.fedorapeople.org/updates/updates-873445.0.img That updates.img blows up. Following procedure, with TC7 DVD: 1. Boot installer 2. Set install package set to 'minimal' 3. Go to disk picker, pick my only disk, and check 'encrypt my data' checkbox 4. Check the custom partitioning checkbox 5. In custom partitioning, delete existing partitions, then click on /boot boom - explodes with 'NameError: global name 'changed_encryption' is not defined correction to 5: I clicked on /, not /boot. Updated updates.img: http://dlehman.fedorapeople.org/updates/updates-873445.1.img That one's good for me. I confirmed the bug without the updates.img with the following procedure: 1. Boot installer 2. Set install package set to 'minimal' 3. Go to disk picker, pick my only disk, and check 'encrypt my data' checkbox 4. Check the custom partitioning checkbox 5. In custom partitioning, delete existing partitions, then click on /, in the right-hand pane, expand 'options', and uncheck the 'encrypt' checkbox 6. Finish partitioning and start install During partitioning, the installer will crash, with "FormatCreateError: ('invalid device specification', '/dev/mapper/fedora')". Following the same procedure with the .1.img updates image, I get a completed and working installation with no encryption, as expected. We can test other paths to see if any regressions have crept in - just try various combinations of checking or not checking the box prior to custom partitioning and then encrypting or not encrypting devices inside of custom partitioning, with different filesystem types and so on. But this single case demonstrates the fix for me. anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.26-1.fc18 Package anaconda-18.26-1.fc18, lorax-18.22-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.26-1.fc18 lorax-18.22-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17714/lorax-18.22-1.fc18,anaconda-18.26-1.fc18 then log in and leave karma (feedback). anaconda-18.27-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.27-1.fc18 18.26 went stable. Closing. (Bodhi closing of bugs when updates go stable is currently broken). |