Bug 1820912
| Summary: | Fedora Anaconda installer is unable to handle/install on an Encrypted LUKS2 partition | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sreyan Chakravarty <sreyan32> | ||||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 31 | CC: | anaconda-maint-list, jkonecny, jonathan, kellin, vanmeeuwen+fedora, vponcova, wwoods | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | --- | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2020-04-10 20:35:34 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: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Sreyan Chakravarty
2020-04-04 16:19:53 UTC
Created attachment 1676240 [details]
program.log
Created attachment 1676241 [details]
storage log
Created attachment 1676242 [details]
ScreenShot1
Created attachment 1676243 [details]
ScreenShot3
Created attachment 1676244 [details]
ScreenShot2
A workaround is available but this will use LUKS version 1 not LUKS version 2. No way to use LUKS version 2 at this point. https://ask.fedoraproject.org/t/ananconda-cant-handle-lvm-on-luks-setup/6112/6?u=sreyan32 *** This bug has been marked as a duplicate of bug 1668013 *** |