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:
ipxe boot from Satellite 6.5 fails with dracut error.
dracut fatal error "ip=1.2.3.4" unrecognized/unknown value  "1.2.3.4"

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


How reproducible:
consistently

Steps to Reproduce:
1.  Attempt to ipxe boot a host and provision RHEL 8.0 from Satellite 6.5 using the default iPXE template
2.
3.

Actual results:
dracut fatal error "ip=1.2.3.4" unrecognized/unknown value  "1.2.3.4"

Expected results:
The kernel boots successfully and launches anaconda

Additional info:

https://github.com/dracutdevs/dracut/pull/572/commits/6c08e34047fde2824e4cde75856ccbb2b0e59c1e

Setting a blocker? since this is a frequently used option and it must work.

Hi Jason,

were you able to set up an evironment to reproduce this issue? Are you able to verify the fix?

Thank you in advance.

I was informed the RHEL 8 kernel would most likely not take the old ip=1.2.3.4 syntax any longer.  I modified the ipxe template to use the new networking syntax.  

Thanks for this though.  the customer, if they use the network boot parameters manually, which does happen from time to time, prefers the old syntax.

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://access.redhat.com/errata/RHBA-2019:3604