Description of problem:
When installing over NFS, if one enters the path wrong, one must wait a timeout (that is probably ok), but during such timeout, instead of the main hub one has to wait in presence of a gray screen. This defeats the main hub approach.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. go to INSTALLATION SOURCE and select NFS
3. return to the main hub
Anaconda does not return to the main hub, instead a big pause with a gray screen must be waited. After such pause (a couple of minutes) the main hub is shown, and the source was not configured (that is OK, since the path was wrong).
return to the main hub intermediately and do the waiting in the background. Such time can be spent in other parts of the hub.
Normally 192.168.0.80:/var/ftp/pub does work and does not experience any delay nor issue. I was able to install properly (i only tested minimal).
Additional info #2:
I tried the bg parameter but in such case the gray screen seems to be 'permanent', or at least long. +5 minutes and it did not return to the main hub.
I was only able to reproduce it by pointing at a live server that was /not/ setup for NFS. My valid NFS server quickly returned an error if I gave it an invalid pass.
Patch posted to do this work in the background.
anaconda-18.22-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.22-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.23-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18.
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.
(I noticed while testing the NFS regressions in RC1 this appears to be fixed, attempts to contact NFS server happen in the background).