Bug 962485

Expected results: please read "a) The error should NOT happen, but that is probably not related to anaconda, and this is an alpha release anyway."

I am not able to reproduce the bug so I'd need details on the error you are seeing and log files. They can be found in /tmp directory, /tmp/anaconda-tb-* file should contain all informations we need. Could you please attach the file to the report? You can copy the file to USB or try to set up network connection in live environment (instead of anaconda). Thanks.

This issue will be probably fixed by not requiring network connection in installer on Live DVD (skipping the network configuration screen). The connection can be established in Live environment itself if needed.

First, I have to correct one point : this was not with a live-dvd, but with the full installation dvd for fedora 19 alpha.

Then I discovered I could skip this screen without configuring anything at all, but I get trapped later, probably for the same reason (unrelated to anaconda and reported as a network manager bug 962827).

Back to anaconda, I think I should have an official way to skip past a network error with only shows the two possibilities to report (impossible in this case) and to quit. There is a possibility to start a debug process, but I am far from being able to get anything useful from it.

Now, getting the files you want seems to me an impossible task. This is the second screen of installing. How could I start a shell, and mount some permanent device to which copy files from the ramdisk or configure the network ? Well, I finally got this step through, but, doing so I have no error logged.

(In reply to comment #4)
 
> Back to anaconda, I think I should have an official way to skip past a
> network error with only shows the two possibilities to report (impossible in
> this case) and to quit. There is a possibility to start a debug process, but
> I am far from being able to get anything useful from it.
> 

Only fatal errors (crashes) should trigger bug reporting dialog in Anaconda. Network connection fail doesn't belong among them. Nevertheless, to investigate why the crash happened I need the log files.

> Now, getting the files you want seems to me an impossible task. This is the
> second screen of installing. How could I start a shell, and mount some
> permanent device to which copy files from the ramdisk or configure the
> network ? Well, I finally got this step through, but, doing so I have no
> error logged.

You can switch to shell on tty2 (Ctrl-Alt F2) and copy files to USB disk (if possible). The hint to configure network assumed you are in Live environment which is not the case as showed up.

> Only fatal errors (crashes) should trigger bug reporting dialog in Anaconda

This is probably what happens : the issue cannot be a failed network connection (because the network is not even configured, no SSID defined, etc.), but more likely results from a crash while initializing the network driver (similar to the bug reported as bug 962827).

Better try again when this other issue is solved, and I take note of the tty2 suggestion.

anaconda-19.27-1.fc19, pykickstart-1.99.31-1.fc19, python-blivet-0.14-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.27-1.fc19

Package anaconda-19.27-1.fc19, pykickstart-1.99.31-1.fc19, python-blivet-0.14-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-19.27-1.fc19 pykickstart-1.99.31-1.fc19 python-blivet-0.14-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-8322/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.27-1.fc19
then log in and leave karma (feedback).

Package pykickstart-1.99.31-1.fc19, anaconda-19.28-1.fc19, python-blivet-0.14-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pykickstart-1.99.31-1.fc19 anaconda-19.28-1.fc19 python-blivet-0.14-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-8322/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.28-1.fc19
then log in and leave karma (feedback).

pykickstart-1.99.31-1.fc19, anaconda-19.28-1.fc19, python-blivet-0.14-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.