Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 565848
Summary: | LVMError: lvactivate failed for lv_root: Skipping volume group vg_test1148 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> | ||||||||
Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 13 | CC: | anaconda-maint-list, jlaska, jonathan, jturner, radualexandrupopescu, rhe, vanmeeuwen+fedora | ||||||||
Target Milestone: | --- | Keywords: | CommonBugs | ||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | anaconda_trace_hash:b3dcacf45ca17d5e53232c700f8237e33fd6f9c38dcb3b148c40264697f792b8 https://fedoraproject.org/wiki/Common_F13_bugs#existing-luks-volumes | ||||||||||
Fixed In Version: | anaconda-13.35-1.fc13 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2010-03-19 14:46:01 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: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 538274 | ||||||||||
Attachments: |
|
Description
James Laska
2010-02-16 14:31:51 UTC
Created attachment 394555 [details]
Attached traceback automatically from anaconda.
= Steps to reproduce = 1. Initiate install using *only* 2 of 4 previously formatted set of disks 2. Choose basic disk layout 3. Choose "replace all partitions" and select "Encrypt" 4. Enter a passphrase I'll see how reproducable this is and whether it's specific to previous disk contents Created attachment 394560 [details]
Attached traceback automatically from anaconda.
Certainly specific to the previous contents of the disk. Wiping out the disks allows me to proceed past this error. = Reproducer = 1. Install an encrypted partition scheme using default partitions 2. After partitioning is complete, initiate another install 3. Choose default partition scheme and [X] encrypt traceback This is a known issue. Any preexisting lvm configurations using encrypted PVs will exhibit this behavior if you specify that the preexisting encrypted PVs be reformatted (not preserving the encryption). Per discussion with Dave on IRC, I'm adding this to F13Beta and noting for CommonBug documentation for the Alpha. I think this might be common enough to note for Alpha users. Recommended workaround is to disregard the passphrase prompt for existing encrypted partitions. Created attachment 396517 [details]
Attached traceback automatically from anaconda.
steps: 1. System originally contained encrypted lvm. 2. Install a new system on it: a. Delete all old partitions. b. create ext4 /boot, ext4 /, swap manually. *** Bug 571955 has been marked as a duplicate of this bug. *** This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This issue was discussed at the F-13 blocker bug review meeting. It was agreed that this issue represents a Beta blocker. While no specific criteria exists to ensure installing encrypted partitions on a system that already contains encrypted partitions, it was felt that the use case captured by this bug is common enough to consider addressing for F13 Beta. dlehman: do you require additional information on this issue? anaconda-13.35-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.35-1.fc13 anaconda-13.35-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.35-1.fc13 http://git.fedorahosted.org/git/?p=anaconda.git;a=commit;h=2cef4cf3a2c7a22b6d0024c6048815d8ad6d74cc Moving to MODIFIED since this is included in anaconda-13.35-1.fc13 Note, and additional commit addresses this issue (see http://git.fedorahosted.org/git/?p=anaconda.git;a=commit;h=74c6e8cb0cc4dfe21b1d43a920c2ccf33f2c444b) Confirmed this issue no longer occurs with anaconda-13.35-1.fc13 anaconda-13.35-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |