Bug 1040716
Summary: | LVMError: pvcreate failed for /dev/md/00: running lvm pvcreate --dataalignment 1024k /dev/md/00 failed | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||||||||||||||||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||||||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||
Version: | 20 | CC: | anaconda-maint-list, atorkhov, g.kaviyarasu, johannbg, jonathan, kparal, robatino, vanmeeuwen+fedora | ||||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||
Whiteboard: | abrt_hash:7384922cbbebf30bcfb19fa96628828f7ab3b2c07f660169281356812029d18f RejectedBlocker | ||||||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||
Last Closed: | 2015-04-14 19:07:43 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
Adam Williamson
2013-12-12 00:44:04 UTC
Created attachment 835519 [details]
File: anaconda-tb
Created attachment 835520 [details]
File: anaconda.log
Created attachment 835521 [details]
File: environ
Created attachment 835522 [details]
File: journalctl
Created attachment 835523 [details]
File: lsblk_output
Created attachment 835524 [details]
File: nmcli_dev_list
Created attachment 835525 [details]
File: os_info
Created attachment 835526 [details]
File: program.log
Created attachment 835527 [details]
File: storage.log
Created attachment 835528 [details]
File: ifcfg.log
OK, so it can be simplified by dropping the 'check/uncheck encrypt checkbox in VG properties' step: 1. Installation Destination, select both, Done 2. "Encrypt my data", "I want to review/modify", Continue 3. Enter passphrase 4. Add 500MB /boot 5. Add 12GB / : appears as 'luks-fedora-00', 'encrypt' checkbox checked 6. Click 'Modify...' for VG 'fedora', set RAID level to RAID-1, Save 7. Click 'Update settings' 8. Add 2GB swap, appears as 'luks-fedora-01', 'encrypt' box checked 9. Done 10. Accept changes 11. Save passphrase (again) 12. Begin installation it doesn't seem to happen if you don't create another partition after step 7, though. if I leave the swap partition out, it doesn't crash. As already mentioned, it also doesn't crash if I create / and swap, but don't hit 'Update settings' after creating /. Note, whether it crashes or not, if I create the mount points manually this way, they are created as encrypted LVs within an unencrypted VG. If I use the 'autopart' button in custom partitioning ('create them for me'), I get an encrypted VG with unencrypted LVs. (If I do it that way - use autopart, then change the RAID level of the VG that's created - I don't hit any crashes, it works). This inconsistency I've filed as https://bugzilla.redhat.com/show_bug.cgi?id=1040720 . This one looks like it fails the following blocker bug criteria hence proposing... "The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration." as well as the raid criteria... I disagree, which is why I didn't propose it. you can certainly create precisely the layout I was trying to create, in several different ways. it only crashes on one specific path. You can disagree about that precise criteria choosing but anaconda should not crash Reproducing bug 1021507 comment 37 again. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-KDE-x86_64-20-1 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 other involved packages: python-blivet-0.23.9-1.fc20.noarch, python-libs-2.7.5-9.fc20.x86_64 package: anaconda-20.25.15-1.fc20.x86_64 packaging.log: product: Fedora reason: LVMError: pvcreate failed for /dev/md/00: running lvm pvcreate --dataalignment 1024k /dev/md/00 failed release: Fedora release 20 (Heisenbug) version: 20 Created attachment 835813 [details] anaconda-tb for comment 16 Both crashes at command: 19:41:23,608 INFO program: Running... lvm pvcreate --dataalignment 1024k /dev/md/00 19:41:23,711 INFO program: Can't open /dev/md/00 exclusively. Mounted filesystem? 19:41:23,712 DEBUG program: Return code: 5 (In reply to Adam Williamson from comment #11) > OK, so it can be simplified by dropping the 'check/uncheck encrypt checkbox > in VG properties' step: > > 1. Installation Destination, select both, Done > 2. "Encrypt my data", "I want to review/modify", Continue > 3. Enter passphrase > 4. Add 500MB /boot > 5. Add 12GB / : appears as 'luks-fedora-00', 'encrypt' checkbox checked > 6. Click 'Modify...' for VG 'fedora', set RAID level to RAID-1, Save > 7. Click 'Update settings' > 8. Add 2GB swap, appears as 'luks-fedora-01', 'encrypt' box checked > 9. Done > 10. Accept changes > 11. Save passphrase (again) > 12. Begin installation I haven't reproduced this. I used a bit different sizes though - two 10GB drives, and 8GB / with 2GB swap. (In reply to Kamil Páral from comment #19) > I haven't reproduced this. I used a bit different sizes though - two 10GB > drives, and 8GB / with 2GB swap. Tested with adamw's sizes, still no crash. Discussed at Go/No-Go meeting on 2013-12-12 [1]. This is a RejectedBlocker. This bug hasn't been reproduced and the same end result can be achieved via two other methods. [1] http://meetbot.fedoraproject.org/fedora-meeting-2/2013-12-12/ I think this is too intricate to even commonbugs if kparal can't reproduce it as described. 'It may crash if you do this very particular thing...or it may not'? meh. Closing due to lack of reproducer. |