Bug 870570

We actually don't try to re-fetch on purpose, because we were re-fetching perfectly valid repodata.  However that should probably only be skipped if we don't have some sort of error state.

I've been running into this too --- it's seriously annoying if the network config isn't exactly right the first time.  (And anaconda is far too willing to assume that networking doesn't need configuration, anyway.)

Please note that in TC6, network spoke was lying about network being connected in some cases (bug 871129) which should be fixed in anaconda 19.22.

Discussed at 2012-10-31 NTH review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-31/f18beta-blocker-review-6.2012-10-31-16.00.log.txt . Accepted as NTH as this bug can be annoying and difficult to work around sometimes when making network configuration changes. However, as it touches a sensitive code path, we would like to see an updates.img for testing before this gets pushed into anaconda proper (and it'd be nice to see the patch itself too).

Because this is an annoying bug and it is not always obvious how to work around it, proposing as Final NTH.

Is this still happening? There haven't been any new reports in almost a month and there have been many anaconda changes since then.

Yes, it's still broken in F18-Final-TC3.  If you arrive at the main menu with broken network configuration, the "installation source" setup fails, and it's very unobvious how to get anaconda to retry that.  I tested by intentionally giving a wrong DNS server address during manual network configuration (in an environment with no DHCP service).  There seems to be a different bug tickled there in TC3, which is that once you've given a bad DNS address the network spoke fails to notice a correction --- but what's being complained of in this BZ is the installation source spoke's unwillingness to retry either.

Basically, none of this stuff is very willing to recover if you don't get it right the first time.

I filed the other issue as bz #889584

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.