Bug 725249 - inconsistent distributions of anaconda initrd.img make network upgrades very difficult
Summary: inconsistent distributions of anaconda initrd.img make network upgrades very ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-24 16:51 UTC by Paul Lambert
Modified: 2012-08-07 14:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 14:50:27 UTC
Type: ---


Attachments (Terms of Use)

Description Paul Lambert 2011-07-24 16:51:52 UTC
Description of problem:  Initially, I was unable to install F15 using preupgrade.  The problem was the released initrd-img (5/13/2011) boot file.  I was able to get around this problem by finding a copy of initrd-img compiled on 5/14/2011 or later.  But, even this was not easy as I found one copy that did not have any networking included.  After hours of searching I did find one that did and the installer asks which network to use and installs the drivers and proceeds from there.

In the course of this activity there were countless hours of debugging time consumed that could have been avoided if 1) the mirrors were all updated in a timely manner and 2) all compiled version of initrd-img include the latest features such as auto detection and configuration of the network devices.

An additional question somewhat related is, "can grub be configured to enable networking?" so that even if the installer does not include this feature the network will already be up.


Version-Release number of selected component (if applicable):
initrd-img 5/13/2011

How reproducible:  everytime


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


Expected results:  


Additional info:

grub.conf 

title Fedora 15 Rescue Reinstall 
	root(hd0,0)
	kernel /vmlinuz-install
	initrd /initrd.img-install

Comment 1 Chris Lumens 2011-07-24 21:35:27 UTC
Well, the initrd is going to change every time a new tree is composed so as to take into account the changes in all the various components.  Making sure they are just always the same isn't possible, or we won't be able to fix any bugs.  In order to say anything definite here, though, I need to know where you downloaded each initrd from.  URLs would be helpful.

Comment 2 Paul Lambert 2011-07-24 23:55:09 UTC



Below are all of my ftp sessions from .bash_history.  I can't say for sure without investing a lot more time which ones are the ones I actually downloaded from.

Here is another way to resolve this. 

1) the initrd.img file that was installed using preupgrade would not boot my HP-Pavilion dv7 AMD Turion x2.  It was dated 5/13/2011.

2) the initrd.img file size of the ones that did boot the installer and had "smart" networking is 98678344.  These initrd.img files came from directory .../releases/15/Fedora/x86_64/os/isolinux/ and were dated 5/14/2011 or later.

3) the initrd.img file size of the one that did boot the installer and did NOT have "smart" networking is 98341632 and was dated 5/13/2011.  This file came from directory .../releases/15/Fedora/i386/os/isolinux/

The installer display size while in char mode was larger in 3) than in 2).  In 3) after answering the MBR question a "no network" error message was displayed.  In 2) after answering the same question a network selection dialog box was presented that included a drop down menu for me to choose which hardware network device I want to use for the install.

When I stated "features" I meant capability with regards to all instances of initrd.img including smart network software.


from my .bash_history file
ftp ftp.fedora.con
ftp ftp.cru.fr
ftp ftp.cru.fr
ftp ftp.cru.fr
ftp redhat.linux.ee
ftp mirrors.kernel.org
ftp mirrors.kernel.org
ftp ftp.iinet.net.au
ftp ftp.iinet.net.au
ftp freshrpms.net
ftp ftp.freshrpms.net
ftp ftp.lip6.fr
ftp ftp.lip6.fr
ftp ftp.saix.net
ftp ftp.saix.net
ftp ftp.saix.net
ftp mirror.optus.net
ftp mirrors.optus.net
ftp mirrors.163.com
ftp ftp.mirrors.163.com
ftp ftp.swin.edu.au
ftp mirror.optus.net
ftp mirror.optus.net

Comment 3 Paul Lambert 2011-07-25 03:30:42 UTC
I incurred several module loading errors when the initrd.img installer booted.  I was unable to find a log where I could determine which ones as during the boot process they just flashed across the screen.  I saw no references to these errors in the anaconda.log file.  This seemed to be present when booting the initrd.img file that did not have smart networking software. (3)

Comment 4 Chris Lumens 2011-08-01 18:30:06 UTC
I don't follow what you mean by "smart networking software".  Also, this really just sounds like you either hit a transient error in one version of the initrd or you just happened to download at a time when mirrors were syncing.

Comment 5 Paul Lambert 2011-08-01 18:38:41 UTC
No, I experienced two different versions of the anaconda installer.  One could not detect the network hardware and had no capability to install drivers to activate the network hardware.  The second anaconda installer had software that detected the hardware (smart/intelligent software), presented a drop down menu from which to choose the network hardware to use and then installed the drivers activating the network thus enabling a network install.

An additional comment regarding the fedora mirrors is that many are obsolete, as they do not have a version of Fedora since 11 or 12.  The mirror list needs to be pruned to include only those sites who want to keep a current and active Fedora distro.

Comment 6 Chris Lumens 2011-08-03 15:06:55 UTC
Please let me know if you are able to reproduce this with F16.

Comment 7 Paul Lambert 2011-08-03 16:34:48 UTC
I still have the initrd.img (-install) and vmlinuz (-install) executables on my system.  How do I determine what version they are? This might help.  Will look to perform a network upgrade to F16 and repost then.

Comment 8 Fedora End Of Life 2012-08-07 14:50:30 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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