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:
Currently it is possible to convince anaconda to attempt a network installation based on settings that are no longer in use.

Version-Release number of selected component (if applicable):anaconda-19.31.123-1


How reproducible:100%


Steps to Reproduce:
1.boot off of netboot.iso
2.configure all settings for a valid connection to the RHEL yum repo
3.reconfigure the network to an address with no connectivity
4.Begin installation

Actual results:
Anaconda formats the drives and then, after a long wait, produces an error that the repo timed out

Expected results:
When the network settings are changed, access to the installation sources is validated to ensure it still works.

Additional info:

https://github.com/rhinstaller/anaconda/pull/411

Seems to resolve my use cases.

If one boots only boot.iso without any installation source specified anaconda still tries to verify the empty source and thus renders installation source and software selection spokes unclickable for approximately 30 seconds after entering the main configuration screen. The check happens again after turning on the network so user has to wait for another 30 seconds to finally set the installation source.

This should be probably fixed.

During verifying this bug I found two more issues: #1358778 and #1358788

PR: https://github.com/rhinstaller/anaconda/pull/712

Verified on RHEL-7.3-20160817.1 with anaconda-21.48.22.82-1.el7.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2158.html