Red Hat Bugzilla – Bug 446371
Anaconda doesn't detect old network configuration, stalls at "Retrying package download"
Last modified: 2008-10-21 16:46:02 EDT
Description of problem:
I tried preupgrade to upgrade from Fedora 8 to 9, it downloaded packages about
6.2 GB in total. Then I rebooted into Anaconda to perform upgrade. Anaconda
finds the old partitions correctly but doesn't activate the network connections.
Maybe it tries to but only DHCP over plain ethernet. I have an ADSL connection
via an ADSL modem not a router. pppoe configuration is not pulled from the
installed Fedora 8. Anaconda stalls at "Retrying package download". I killed it
after about a minute.
Version-Release number of selected component (if applicable):
3 out of 3 tries.
Steps to Reproduce:
Cannot perform upgrade
Anaconda should detect the network configuration and start it if network
activity is expected.
Which package is it trying to download, and what version of preupgrade did you use?
The anaconda dialog didn't tell the package name, only "Retrying package download".
I started with preupgrade-0.9.3-1 then I killed it when 0.9.3-2 came out (0.9.3
was already downloading packages) and upgraded to the new one. I restarted with
the new one and it continued downloading packages. Then it hung at the last
download phase so I killed it again. This probles was solved by 0.9.3-3 that
finished the procedure and offered the "reboot now" button.
It doesn't _stall_ for me, but 0.9.3-3 does not retain the existing network
configuration and makes me re-enter this information (which is an annoyance).
Thus, when rebooting, I must tell it that I have IPv4, that I don't have IPv6,
and must give my static IP address, mask, gateway address, and DNS hosts.
PreUpgrade should be able to get all that info from the current config. Perhaps
PreUpgrade could add the network info to the grub.conf file?!?
Not really - anaconda can't set up every possible network configuration that you
might been using on your system (e.g. wireless with WPA, VPN, etc)
The *proper* solution is to make sure we download all the right packages first
so you don't *need* the network.
I re-tried with 0.9.3-3 from scratch by deleting /var/cache/yum/anaconda-upgrade
and the old preupgrade GRUB entry but the only change was that in the new GRUB
entry the method= parameter had a different mirror. It still stalls at starting
upgrade after discovering package dependencies, giving the same dialog with
empty title bar and the message is "Retrying package download". Ctrl-Alt-F2 and
"ip addr" shows no established network.
(In reply to comment #4)
> Not really - anaconda can't set up every possible network configuration that
> might been using on your system (e.g. wireless with WPA, VPN, etc)
> The *proper* solution is to make sure we download all the right packages first
> so you don't *need* the network.
I believe this happens because of new packages installed *after* preupgrade
finished download everything. I left the "reboot now" window hanging around and
kept on yumming new stuff... had to re-enter my network parameters on anaconda.
Maybe the best solution would be to leave the new packages as they are, if
anaconda can't reach the internet... upgrade only the ones preupgrade
Sure, that's a good idea, but we can't change the behavior of F9 anaconda,
because it's frozen as part of the release. So that's not going to work.
There's a workaround for missing kernel packages on i386 installs, but 64-bit
machines (x86_64/ppc64) will end up with missing packages because of differences
between F8 yum and anaconda.
I'm not sure we can fix that problem for F8->F9. We might have to wait until
F10. Luckily F10Alpha is only 8 weeks away or so.
This is fixed in Fedora 10's anaconda + preupgrade 0.9.8.