Bug 1039662 - hang on launch when existing installation is LVM thin provisioning on LUKS
Summary: hang on launch when existing installation is LVM thin provisioning on LUKS
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F20FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2013-12-09 17:31 UTC by Chris Murphy
Modified: 2013-12-10 02:08 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-10 02:08:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.log (2.76 KB, text/plain)
2013-12-09 17:35 UTC, Chris Murphy
no flags Details
program.log (16.47 KB, text/plain)
2013-12-09 17:35 UTC, Chris Murphy
no flags Details
storage.log (50.12 KB, text/plain)
2013-12-09 17:35 UTC, Chris Murphy
no flags Details
journalctl (74.19 KB, text/plain)
2013-12-09 17:36 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2013-12-09 17:31:57 UTC
Description of problem:
When launching the installer on a system with a disk containing a previous installation that uses LVM Thin Provisioning, the installer hangs on launch.

Version-Release number of selected component (if applicable):
anaconda 20.25.14-1

How reproducible:
Always

Steps to Reproduce:
1. DVD ISO TC5 install, guided partitioning LVM Thin Provisioning, encrypted.
2. Confirm successful reboot from installation.
3. Boot the installer again...

Actual results:
Hang on launch.

Expected results:
Should let me choose language and proceed to hub.

Additional info:

Comment 1 Chris Murphy 2013-12-09 17:35:17 UTC
Created attachment 834419 [details]
anaconda.log

Comment 2 Chris Murphy 2013-12-09 17:35:28 UTC
Created attachment 834420 [details]
program.log

Comment 3 Chris Murphy 2013-12-09 17:35:40 UTC
Created attachment 834421 [details]
storage.log

Comment 4 Chris Murphy 2013-12-09 17:36:04 UTC
Created attachment 834422 [details]
journalctl

Comment 5 Chris Murphy 2013-12-09 18:18:39 UTC
With the original 5TB qcow2, this was 100% reproducible. The qcow2 was bootable just fine. However anaconda would hang at launch if this qcow2 was the backing for the single /dev/vda device.

However, I can't create another qcow2 that behaves this way so far.

Comment 6 Kamil Páral 2013-12-09 18:20:31 UTC
I tried to reproduce it, but anaconda starts as normal, no problems, no hang.

Comment 7 Mike Ruckman 2013-12-09 18:21:49 UTC
Discussed in 2013-12-09 Blocker Review meeting [1]. Voted to punt because it looks like there is a real problem but cmurf lost the image that reproduces it and cannot immediately recreate it; we will delay the determination until we can say whether it's plausible to block on the bug (can reproduce it again, or tell what's going on from the trace).

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-09/

Comment 8 Chris Murphy 2013-12-10 02:08:04 UTC
I've tested this 6 ways to Sunday and cannot reproduce.


Note You need to log in before you can comment on or make changes to this bug.