RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
If you choose to install e.g. from http, and you do some networking change, the repository availability is not re-checked afterwards.

Version-Release number of selected component (if applicable):
2013-11-05 nightly

How reproducible:
always

Steps to Reproduce:
1. start network installation
2. at the overview screen, go to networking settings
3. just turn the network off, go back to overview
4. try to configure the installation repository
5. turn the network on

Actual results:
there is "Error setting up base repository" and you cannot install
going to repository configuration and confirming the configuration does not help

Expected results:
a) the error about repository config (which you should get after step 3) is more specific to give a clue what is wrong (see bug 1025398)
b) after activating the network in step 5, you can continue the installation without any other magic from user side

Additional info:

I don't think that triggering a recheck on changes in the network is feasible, since there may be intermittent issues that we'd better to ignore, and there may be issues elsewhere in the network unrelated to the network configuration for which we'd also want to recheck.

A better solution would be to recheck uninitialized repositories any time the source spoke is entered and the user hits "Done", regardless of whether the settings were changed. Such a change is handled in bug 1030997

*** This bug has been marked as a duplicate of bug 1030997 ***