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:

This is a continuation of dracut BZ #2212804 and anaconda BZ #2212810.
When customers try to install systems over the network and something goes wrong while retrieving stage2 image, they eventually get access to the dracut prompt.

Unfortunately troubleshooting from that prompt is nearly impossible, because standard tools such as "ping" and "arping" are not shipped anymore.

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

anaconda-dracut-33.16.8.9

How reproducible:

Always

Steps to Reproduce:
1. Setup a QEMU/KVM with isolated network (no DHCP)
2. Boot by specifying kernel and initrd paths and "ip=someip::... inst.repo=xxx" as kernel args

   (repo pointing to unreachable network)

Actual results:

Can't debug easily

Expected results:

Can try pinging, arpinging, etc.

Additional info:

This is critical for a lot of customers, because tuning network install snippets is not that easy.

This problem is reported in bug 2210315 against dracut, so I'm closing this one as a duplicate.

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