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 1307148 - Unable to set static IP when booting from install DVD using ip= parameter
Summary: Unable to set static IP when booting from install DVD using ip= parameter
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: dracut-maint
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-12 20:20 UTC by Rayford Johnson
Modified: 2019-02-25 15:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-15 09:01:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rayford Johnson 2016-02-12 20:20:24 UTC
Description of problem:

I'm unable to set static network details for an interface by passing parameters when booted to install DVD.  I"m using parameters from 20.1. Configuring the Installation System at the Boot Menu <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Installation_Guide/index.html#sect-boot-options-installer>.


How reproducible:

Always.

Steps to Reproduce:

1.  Boot RHEL7.2 installation DVD [1]
2.  Select [I]nstall
3.  Press <TAB> to edit
4.  Append a valid network configuration [2]
5.  Proceed with boot to install

[1]: SHA-256: 03f3a0291634335f6995534d829bd21ffaa0d000004dfeb1b2fb81052d64a4d5  RHEL-7.2-20151030.0-Server-x86_64-dvd1.iso downloaded from access.redhat.com

[2]: Example,  ip=192.168.10.15::192.168.10.254:host15:em1:none

Actual results:

dracut: FATAL: For argument 'ip=192.168.10.15::192.168.10.254:host15:em1:none'\nSorry, setting client-ip does not make sense for 'dhcp'
dracut: Refusing to continue



Expected results:
Static network configuration applied to interface; installation proceeds.


Additional info:

https://bugzilla.redhat.com/show_bug.cgi?id=836039

The only way I was able to get connected to the network to perform a non-interactive kickstart network install was to put a dhcp server on the network.  ip=em1:dhcp worked; the system pulled its kickstart and proceeded to perform an installation completely without interaction.

Comment 2 Rayford Johnson 2016-02-12 20:33:24 UTC
Turns out it's user error.  Apparently, I've been reading the docs/parameter wrong this whole time even as meticulous as I've attempted to be.  I was sure I was getting everything correct and it was failing me as a bug.  Please let me know how I should proceed to close this properly.  Should I just set Status: CLOSED?

Comment 3 Jan Stodola 2016-02-15 09:01:48 UTC
Closing the bug per comment 2.

Comment 4 Don Krajewski 2019-02-25 14:59:08 UTC
Comment 2 is not viewable. The rest of bug #1307148 is viewable. Can there be something on Comment #2 that can be made public? Thanks.

Comment 5 Rayford Johnson 2019-02-25 15:10:33 UTC
(In reply to Don Krajewski from comment #4)
> Comment 2 is not viewable. The rest of bug #1307148 is viewable. Can there
> be something on Comment #2 that can be made public? Thanks.

Don, I believe it's now public.  I didn't realize when I posted the comment in-reply to my submission that it defaulted to private.

Comment 6 Don Krajewski 2019-02-25 15:48:46 UTC
Thank you. 

Don


Note You need to log in before you can comment on or make changes to this bug.