| Summary: | LVMError: lvactivate failed for root: running lvm lvchange -a y fedora/root failed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, kparal, lbrabec, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-04-23 09:52:26 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: | |||||
| Attachments: |
|
||||||
|
Description
Kamil Páral
2013-12-03 11:41:33 UTC
Created attachment 832006 [details]
anaconda-tb
I could reproduce it as long as I deleted all contents and tried to create yet another LVM on mdraid 10. Once I tried to create default LVM (without mdraid) setup, installation worked ok. I'm unclear why anaconda tries to activate the older VG, when I chose to remove it and create a fresh new one. Maybe because the name of the old one and the name of the new one is the same? Is is possible that it tries to reuse it instead of re-creating it? Is this reproducible in F21 or F22? I tried to reproduce this bug with F22 Beta RC3, installation worked as expected, no bug encountered. |