This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2212804 - dracut prompt is never reached when requiring networking but no DHCP is listening on the network
Summary: dracut prompt is never reached when requiring networking but no DHCP is liste...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dracut
Version: 8.8
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: dracut-maint-list
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-06 12:18 UTC by Renaud Métrich
Modified: 2023-09-20 23:25 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 23:25:42 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5721 0 None Migrated None 2023-09-20 23:25:36 UTC
Red Hat Issue Tracker RHELPLAN-167714 0 None None None 2023-09-20 23:25:40 UTC

Description Renaud Métrich 2023-06-06 12:18:43 UTC 
Description of problem:

When customers try to install systems over the network and specify nothing for "ip" parameter (hence defaulting to DHCP), but a inst.repo for example, dracut tries forever to get the IP address over DHCP.
If there is no DHCP service listening, which is very common, then the system waits several hours until dracut emergency prompt is reached.
The only message we see is:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
         Starting dracut initqueue hook...
[    9.426013] TECH PREVIEW: NVMe/TCP may not be fully supported.
[    9.426013] Please review provided documentation for limitations.
[    9.751210] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[    9.752011] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[    9.752538] 8021q: adding VLAN 0 to HW filter on device enp1s0
[    9.759817] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[    9.761097] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[    9.824009] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Then nothing happens, which is quite confusing, because the admin doesn't know what's happening at all.

Booting with rd.debug, we can see that the initqueue loop iterates "slowly" (~ every 100 seconds), so eventually, after days, the dracut prompt will be reached:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
[  828.546445] dracut-initqueue[843]: /bin/dracut-initqueue@68(main): main_loop=9
 :
[  919.551251] dracut-initqueue[843]: /bin/dracut-initqueue@68(main): main_loop=10
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

We need something to drop early, e.g. some absolute timeout, but also we need to report what is currently being waited for.

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

dracut-049

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 "inst.repo=xxx" as kernel args

Actual results:

After 900 seconds, still at loop 10

Expected results:

After 180 seconds (the rd.retry default), getting the dracut prompt + regular messages stating "Getting IP address over DHCP" or similar

Additional info:

This is critical for a lot of customers, because DHCP is rarely used
Comment 1 RHEL Program Management 2023-09-20 23:25:05 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 2 RHEL Program Management 2023-09-20 23:25:42 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.
Note You need to log in before you can comment on or make changes to this bug.