Bug 862883

Summary: anaconda crash if existing filesystem is btrfs
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, dcantrell, g.kaviyarasu, jonathan, 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: 2012-10-03 22:06:22 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 Flags
pyhook anaconda crash log tar bz2 none

Description Chris Murphy 2012-10-03 20:06:53 UTC 
Created attachment 621123 [details]
pyhook anaconda crash log tar bz2

Description of problem:
If btrfs volume is present, anaconda crashes on launch.

Version-Release number of selected component (if applicable):
F18 Beta TC1
anaconda-18.11-1.fc18.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Ensure a disk or partition has a btrfs file system (empty is fine)
2. Launch installer
  
Actual results:
Crash. /var/messages contains:
Oct  3 15:51:51 localhost abrt: detected unhandled Python exception in '/usr/bin/anaconda-cleanup'
Oct  3 15:51:52 localhost anaconda: /sbin/anaconda 18.11

Expected results:
No crash.

Regression results:
If btrfs is not present the problem does not occur. If I format any partition or disk btrfs, and then relaunch anaconda/installer, it crashes.

Additional info:
Testing in a Virtual Box 4.2.0 VM.
Attaching crash logs folder.
Comment 1 Jesse Keating 2012-10-03 22:06:22 UTC 
Marking it a dupe of what I think is the same problem, but I'm not bothering to unpack the archive to look at your traceback.

*** This bug has been marked as a duplicate of bug 862742 ***