Bug 437858
Summary: | LiveUSB Anaconda Crashes with encrypted /dev/md0 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Warren Togami <wtogami> |
Component: | anaconda | Assignee: | David Lehman <dlehman> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | ||
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: | 2008-04-18 20:33:29 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
Warren Togami
2008-03-17 19:15:33 UTC
Created attachment 298296 [details]
OSError: [Errno 2] No such file or directory: '/dev/mapper/luks-md0'
Created attachment 298297 [details]
KeyError: 'crypt_LUKS'
Rebooting into the same LiveUSB, anaconda crashes earlier when it sees the now
existing encrypted /dev/md0 from the previous attempt.
anaconda-11.4.0.53-1.x86_64 The first crash happens in F9 Alpha LiveUSB, but not the second crash. This is still broken in F9 Beta LiveUSB. But interestingly, this type of install works fine from a non-live anaconda install. Created attachment 298739 [details]
make sure root device is set up before trying to use it in a live install
This is completely untested. Looks like at least a big step in the right
direction based on a quick look at the code.
Created attachment 298744 [details]
setup the device and account for the full path returned by setupDevice
Created attachment 298746 [details] anaconda.log Got past the crash in Comment #1 with your one-liner patch. But it crashed a bit later. Here is the anaconda.log from that crash. Fix (path from comment #7) will be in anaconda-11.4.0.56-1. My understanding is that this bug was fixed in anaconda-11.4.0.56-1. Please reopen if that is not the case. |