Bug 442593

Summary:	Fedora 9 beta problem - upgrade from Fedora 8 fails to install boot loader
Product:	[Fedora] Fedora	Reporter:	Jussi Eloranta <eloranta>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	low
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-04-15 21:10:47 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 Jussi Eloranta 2008-04-15 18:16:47 UTC

Description of problem:

I tried to upgrade from Fedora 8 to Fedora 9 beta. Installation of all rpms went
fine but anaconda crashed when installing the bootloader (grub). I clicked on
the debug option and the console screen shows:

TypeError: coercing to Unicode: need string or buffer, instance found

before this I see bunch of messages - apparently a traceback:

progress_gui.pu 80
gui.py 1267

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

Fedora 9 beta.
How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jeremy Katz 2008-04-15 18:36:28 UTC

Can you attach the actual traceback you received?

Comment 2 Jussi Eloranta 2008-04-15 21:07:33 UTC

Well, since this was during the installation, I could not print etc.

I wrote down some more info. For gui.py the line was something like (I don't
have more info on the previous lines - sorry):

gui.py line 1267, in handleRenderCallback
self.currentWindow.renderCallback()

and after that appeared the TypeError:...

below that was:

/usr/lib/python2.5/posixpath.py(173)exists()
-> return false
and after this I got the "debugger prompt"

By the way, the boot loader worked after this - although it was installed there
before since this was an upgrade.

Comment 3 Jeremy Katz 2008-04-15 21:10:47 UTC


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