Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 596993 - Anaconda causes OOM during upgrade
Summary: Anaconda causes OOM during upgrade
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ales Kozumplik
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-27 21:20 UTC by James Vega
Modified: 2014-09-30 23:39 UTC (History)
4 users (show)

Fixed In Version: anaconda-14.7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-08-16 22:29:13 UTC

Attachments (Terms of Use)

Description James Vega 2010-05-27 21:20:07 UTC
Description of problem:
In trying to upgrade from F12 to F13 via preupgrade, the install kept dying after downloading install.img.  One of the attempts, I switched to VT4 to watch the message logs and saw that the OOM killer was trashing anaconda, and a few other things along the way.  Since this was a VM (VirtualBox 3.2.0), I changed the allocated memory from 256 MB to 384 MB and this time anaconda was able to get far enough to tell me that there wasn't enough memory for the graphical installer, so the text installer would be used instead.

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

How reproducible:
Happened every time I tried to upgrade with 256 MB allocated to the VM.

Steps to Reproduce:
Actual results:
OOM killer gets triggered while anaconda does initial setup after install.img is downloaded.

Expected results:
Low memory conditions are detected and text installer is used.

Comment 1 Ales Kozumplik 2010-05-28 08:34:54 UTC

thanks for the report. the fix won't make f13 so I'm moving it to rawhide.


Comment 2 Ales Kozumplik 2010-05-28 08:36:00 UTC

did you say 'downloading install.img'? Does it mean you used http or ftp method for the install?


Comment 3 James Vega 2010-05-28 14:02:04 UTC
I used preupgrade to prep the upgrade, but there wasn't enough space in /boot for everything that preupgrade needed to stash there.  So, when I rebooted to perform the upgrade, it downloaded install.img.

Comment 4 Ales Kozumplik 2010-06-01 13:46:24 UTC
Fixed in anaconda-14.7 by commit 9735b2bd5c98dbe310ed666c1194a25f3d825b7f.

Comment 5 Bug Zapper 2010-07-30 11:44:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:

Comment 6 Alan Crosswell 2011-04-01 00:34:04 UTC
Does not appear to be fixed in 14.22.  Fails on a text-mode install with 384 MB.  See release notes documentation bug 691238 that I've filed.  Is this supposed to work in a 384 MB system or not?

Comment 7 Fedora End Of Life 2012-08-16 22:29:15 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here:

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