Description of problem:
Anaconda is still connecting, but in the main hub it says: "connected" which is not true. And might be false in case the connection fails, like what happened to me.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
boot a guest/host in which dhcp for some (yet unknown) reason
does not acquire an ip in the end.
the main hub shows connected, but it is connecting and in the end it fails to connect, so it is important to display 'connecting' instead of 'connected' which is not true.
incorrect status report in them main hub, one might decide to go to installation source and select closest mirror, but there might be no network.
report an accurate status of the network.
this guest does not get an ip for some reason, maybe there are mo more free leases, i will check later. As a workaround i set the ip manually (with some caveats i will try to report later) and it connects ok.
This is fixed in bug 871129 where we more accurately discriminate "Connected" and "Not Connected" (the latter including connecting and disconnecting states). I'll keep this BZ open to add "Connecting...", "Disconnecting..." states eventually.
anaconda-18.28-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.28-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
This bug looks to have been fixed since 18.28 but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.