Bug 489518

Summary:	installer aborts while scanning for storage when disk w/mac partition table is connected
Product:	[Fedora] Fedora	Reporter:	Jarod Wilson <jarod>
Component:	pyparted	Assignee:	Dave Cantrell <dcantrell>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	dcantrell, hdegoede, pjones, rmaximo, vanmeeuwen+fedora
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-06-17 20:24:27 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:

Description Jarod Wilson 2009-03-10 15:15:33 UTC

Anaconda bails out almost immediately after it starts scanning for storage devices if a firewire disk is connected, dumping you back to vt1, where you see:

Running anaconda 11.5.0.25, the Fedora system installer - please wait...
14:44:29 Starting graphical installation...
Running... ['udevadm', 'settle', '--timeout=2']
Running... ['udevadm', 'settle', '--timeout=2']
Running... ['udevadm', 'trigger', '--subsystem-match=block']
Running... ['udevadm', 'settle', '--timeout=2']
python: Objects/stringobject.c:115: PyString_FromString: Assertion 'str != ((void *)0)' failed.
install exited abnormally [1/1]
disabling swap...
unmounting filesystems...
etc.

Comment 1 Chris Lumens 2009-03-12 17:49:10 UTC

Python makes it really hard to tell which module is failing, but I'm going to go out on a limb here and say it's a problem in pyparted.  At the least, we do call PyString_FromString in a bunch of places without checking for NULL first.  I've fixed that up.  Please try the next rawhide which should have a new pyparted build and see if you no longer see this bug.  If it continues to show up, we'll have to figure out which module is causing the problem.

Comment 2 Jarod Wilson 2009-03-18 13:29:39 UTC

Looks like you got it, I'm looking at the partitioning screen now, complete with the firewire drive.

Comment 3 Jarod Wilson 2009-03-24 21:07:00 UTC

I just hit this one again. The FireWire drive was irrelevant. The mac partition table on the drive I originally hit this with seems to be the key -- an internal drive w/a mac partition table just triggered the same thing.

Comment 4 Chris Lumens 2009-03-25 15:46:32 UTC

This could be the string handling in the pyparted libparted exception code.

Comment 5 Hans de Goede 2009-03-26 12:24:32 UTC

(In reply to comment #4)
> This could be the string handling in the pyparted libparted exception code.  

Ack, I believe the abort will be fixed by the patch I've just attached to:
https://fedorahosted.org/pyparted/ticket/3

Then we will probably still get a backtrace, but getting rid of the abort is the
first step in fixing this.

Comment 6 Chris Lumens 2009-03-27 15:48:23 UTC

I just merged this patch in, so this bug should be better in the next build of pyparted.  Of course we will still have the backtrace to contend with, but that should be easy.

Comment 7 Bug Zapper 2009-06-09 12:05:24 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Jarod Wilson 2009-06-17 20:24:27 UTC

Finally got around to checking on this one. The abort is gone, but I still run into bug 498602. Will continue the discussion there, closing this bug.