Description of problem: After an installation source fails the check, reverting to "Closest Mirror" doesn't clear the error. Re-choosing your software selection *seems* to work, but I can't get it to complete an install after introducing on error in the config. Version-Release number of selected component (if applicable): anaconda-22.18-1 How reproducible: Always Steps to Reproduce: 1. Boot into a text installation 2. Enter bad url for installation source 3. Watch it fail the check 4. Revert back to "Closest Mirror" Actual results: Error never clears and you can't continue the installation Expected results: Error clears with new setting, installation can continue Additional info: Tested this several times in an x86_64 kvm instance.
Do you mean that the status doesn't update automatically when the source status changes? Does the status update when you hit r to refresh? The TUI isn't a ncurses interface. It's intended as line-based output so it can be run all sorts of annoyingly simple terminals.
The status doesn't update when you change the setting in question or when you refresh the view. Once that error shows up, it seems to stay there.
Proposed as a Blocker for 22-final by Fedora user roshi using the blocker tracking app because: I believe this bug is a conditional violation of the "Installation interfaces" Final criterion: "The installer must be able to complete an installation using all supported interfaces. "
Discussed at 2015-02-16 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2015-02-16/f22-blocker-review.2015-02-16-17.30.log.txt . Accepted as a Final blocker as a conditional violation of the criterion cited in c#3 - any encounter of an error condition during a text install seems to be unrecoverable.
Changing the version on this since it's been accepted as an F22 blocker. Also, pushed the patch which should fix this, to f22-branch and master.
python-blivet-1.0.1-1.fc22, anaconda-22.20.2-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/anaconda-22.20.2-1.fc22,python-blivet-1.0.1-1.fc22
Package python-blivet-1.0.1-1.fc22, anaconda-22.20.2-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-blivet-1.0.1-1.fc22 anaconda-22.20.2-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-3110/anaconda-22.20.2-1.fc22,python-blivet-1.0.1-1.fc22 then log in and leave karma (feedback).
anaconda-22.20.3-1.fc22, python-blivet-1.0.2-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/python-blivet-1.0.2-1.fc22,anaconda-22.20.3-1.fc22
anaconda-22.20.2-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/anaconda-22.20.2-1.fc22
anaconda-22.20.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.