Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When installing using a kickstart and a broken "repo" is specified, the installation fails as "[!] Installation source" but no error pops up to help the admin understand what is going on.
Only checking for ERR in /tmp/anaconda.log can give some tip:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
13:10:33,848 DBG payload: retrieving treeinfo from http://192.168.122.1/rhel82 (proxy: ; sslverify: True)
13:10:33,854 DBG payload: getting release version from tree at http://192.168.122.1/rhel82 (8.2)
13:10:33,855 DBG payload: using treeinfo release version of 8.2
13:10:36,207 ERR payload: PayloadError: Failed to download metadata for repo 'BaseOS': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
13:10:36,207 DBG payload: Updating payload thread state: -1
13:10:36,210 DBG payload: getting release version from tree at None (8.2)
13:10:36,210 DBG payload: using default release version of 8.2
13:10:37,058 DBG payload: Source http://192.168.122.1/rhel82 needs network for installation
13:10:37,100 DBG payload: Source http://192.168.122.1/rhel82 needs network for installation
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
In the example above, an invalid "BaseOS" repo was specified, this leads to the error, but due to the last lines being "Source http://192.168.122.1/rhel82 needs network for installation" (a path to a DVD mounted on HTTP), the admin can believe there is an issue with the Network configuration instead.
Version-Release number of selected component (if applicable):
anaconda-29.19.2.17-1.el8
How reproducible:
Always
Steps to Reproduce:
1. Boot over the network with a kickstart referring to an invalid repository
Excerpt:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
repo --name="Dummy" --baseurl=file://non/existent
url --url=http://192.168.122.1/rhel82
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Actual results:
Starting installer, one moment...
anaconda 29.19.2.17-1.el8 for Red Hat Enterprise Linux 8.2 started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
* if the graphical installation interface fails to start, try again with the
inst.text bootoption to start text installation
* when reporting a bug add logs from /tmp as separate text/plain attachments
13:17:51 Not asking for VNC because of an automated install
13:17:51 Not asking for VNC because text mode was explicitly asked for in kickstart
Starting automated install..
Generating updated storage configuration
Checking storage configuration...
================================================================================
================================================================================
Installation
1) [x] Language settings 2) [x] Time settings
(English (United States)) (America/New_York timezone)
3) [!] Installation source 4) [!] Software selection
(Error setting up software (Error checking software
source) selection)
...
Expected results:
Some error message explaining the issue.
Comment 3RHEL Program Management
2023-09-18 15:00:31 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4RHEL Program Management
2023-09-18 15:02:20 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.