Bug 499215

Summary: anaconda exits on virtio install
Product: [Fedora] Fedora Reporter: Pierre Ossman <pierre-bugzilla>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: anaconda-maint-list, jgranado, rmaximo, vanmeeuwen+fedora
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: 2009-09-09 12:05:14 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 Flags
screen shot none

Description Pierre Ossman 2009-05-05 16:06:18 UTC 
There are two sed expressions in grub-install that haven't been updated to handle virtio disks (/dev/vd*). The version in rawhide has the fix though so all that is needed is to push that update to F10.

Anaconda crashes during the final stages of installation, probably because of this (included screen shot). A respin of the installation media would be nice.
Comment 1 Peter Jones 2009-05-05 18:47:21 UTC 
The screenshot doesn't appear to have been attached.
This probably isn't why anaconda is giving a traceback; it doesn't call grub-install.  Regardless of that, we don't do installation media respins.
Comment 2 Pierre Ossman 2009-05-05 21:41:10 UTC 
Created attachment 342539 [details]
screen shot

I wonder where that went... Oh well, attempt #2.

And it seems you are right. I fixed up grub-install as anaconda was installing packages, and it still crashed the same way.
Comment 3 Chris Lumens 2009-05-08 13:07:01 UTC 
Could you please retest with a prerelease of F11?  There have been significant changes to the storage and bootloader sections of anaconda which makes it very difficult to determine whether or not your bug still exists.  Thanks.
Comment 4 Joel Andres Granados 2009-09-09 12:05:14 UTC 
Its been a long time since this bug has been addressed.  Having reached f12 alpha, it probably has been fixed.  Feel free to reopen this issue if you continue to see this behavior.