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 2212810 - dracut prompt is never reached when malformed ip= parameter is specified on the kernel command line
Summary: dracut prompt is never reached when malformed ip= parameter is specified on t...
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:32 UTC by Renaud Métrich
Modified: 2023-09-20 23:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 23:35:56 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-5728 0 None Migrated None 2023-09-20 23:35:53 UTC
Red Hat Issue Tracker RHELPLAN-159065 0 None None None 2023-06-06 12:38:01 UTC

Description Renaud Métrich 2023-06-06 12:32:46 UTC 
Description of problem:

This is a continuation of dracut BZ #2212804.
When customers try to install systems over the network and specify a malformed ip= kernel command line parameter, the dracut emergency prompt is eventually reached after a very long time (~1 hour), instead of somehow expected 4/5 minutes.
During all that time, we can only see the following message regularly (every ~10 seconds):
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
[  642.665130] dracut-initqueue[5561]: Warning: Downloading 'http://192.168.122.1/rhel88/images/install.img' failed!
[  642.670886] dracut-initqueue[5576]:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
[  642.670943] dracut-initqueue[5576]:                                  Dload  Upload   Total   Spent    Left  Speed
[  645.729126] dracut-initqueue[5576]:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0curl: (7) Failed to connect to 192.168.122.1 port 80: No route to host
[  645.738017] dracut-initqueue[5570]: Warning: Downloading 'http://192.168.122.1/rhel88/LiveOS/squashfs.img' failed!
[  645.738805] dracut-initqueue[940]: Warning: anaconda: failed to fetch stage2 from http://192.168.122.1/rhel88
[  648.823442] dracut-initqueue[940]: Warning: can't find installer main image path in .treeinfo
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

The issue also happens if the ip= is properly specified but the network is not functional, e.g. because the network requires a VLAN specification but it was not specified on kernel command line.

We need something to drop early, e.g. some absolute timeout.

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

dracut-049
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:

After 900 seconds, still at loop 90 (over 240)

Expected results:

After 180 seconds (the rd.retry default), getting the dracut prompt

Additional info:

This is critical for a lot of customers, because tuning network install snippets is not that easy.
Comment 1 Jiri Konecny 2023-06-08 09:27:46 UTC 
Hi Renauld,

I'm switching this bug to Dracut component because I don't think Anaconda has much things to do to fix this from our side.

The point is the `ip` command is Dracut specific which is processed and set by Dracut.
Download of the stage2 is using `fetch_url` method to abstract the curl call (which I expect is the reason for slowing down the main_loop), so we are again not the owners of the download execution code.


Dracut devs, please feel free to reassign this back when you find there is something Anaconda can do to fix this issue.
Comment 2 RHEL Program Management 2023-09-20 23:34:43 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 3 RHEL Program Management 2023-09-20 23:35:56 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.