Bug 1307148 - Unable to set static IP when booting from install DVD using ip= parameter
Unable to set static IP when booting from install DVD using ip= parameter
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: rc
: ---
Assigned To: dracut-maint
Release Test Team
Depends On:
  Show dependency treegraph
Reported: 2016-02-12 15:20 EST by Rayford Johnson
Modified: 2016-02-15 04:01 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-15 04:01:48 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rayford Johnson 2016-02-12 15:20:24 EST
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:


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=

Actual results:

dracut: FATAL: For argument 'ip='\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:


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 3 Jan Stodola 2016-02-15 04:01:48 EST
Closing the bug per comment 2.

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