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 1271656 - MTU/MAC not set in dracut
Summary: MTU/MAC not set in dracut
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1256306 1289485 1313485
TreeView+ depends on / blocked
 
Reported: 2015-10-14 12:44 UTC by Jan Stodola
Modified: 2017-02-09 08:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 07:59:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2530 0 normal SHIPPED_LIVE dracut bug fix and enhancement update 2016-11-03 14:17:01 UTC

Description Jan Stodola 2015-10-14 12:44:18 UTC 
Description of problem:
Dracut allows to set MAC address and MTU for the device being configured. However, it doesn't work in all cases, see the examples bellow:

1) format: ip=<interface>:{dhcp|on|any|dhcp6|auto6}[:[<mtu>][:<macaddr>]]

ip=ens3:dhcp:1000                       MTU:fail  MAC:N/A
ip=ens3:dhcp::54:52:00:ab:cd:ef         fails to boot: Sorry, unknown value 'ab'
ip=ens3:dhcp::[54:52:00:ab:cd:ef]       MTU:N/A   MAC:fail
ip=ens3:dhcp:1000:54:52:00:ab:cd:ef     fails to boot: Sorry, unknown value 'ab'
ip=ens3:dhcp:1000:[54:52:00:ab:cd:ef]   MTU:fail  MAC:fail


2) format: ip=<client-IP>:[<peer>]:<gateway-IP>:<netmask>:<client_hostname>:<interface>:{none|off|dhcp|on|any|dhcp6|auto6|ibft}:[:[<mtu>][:<macaddr>]]

ip=192.168.122.20::192.168.122.1:24:test:ens3:none:1000                      MTU:OK   MAC:N/A
ip=192.168.122.20::192.168.122.1:24:test:ens3:none::54:52:00:ab:cd:ef        MTU:N/A  MAC:OK
ip=192.168.122.20::192.168.122.1:24:test:ens3:none::[54:52:00:ab:cd:ef]      MTU:N/A  MAC:fail
ip=192.168.122.20::192.168.122.1:24:test:ens3:none:1000:54:52:00:ab:cd:ef    MTU:OK   MAC:fail
ip=192.168.122.20::192.168.122.1:24:test:ens3:none:1000:[54:52:00:ab:cd:ef]  MTU:OK   MAC:fail

ip=::::test:ens3:dhcp:1000                       MTU:fail  MAC:N/A
ip=::::test:ens3:dhcp::54:52:00:ab:cd:ef         MTU:N/A   MAC:fail
ip=::::test:ens3:dhcp::[54:52:00:ab:cd:ef]       MTU:N/A   MAC:fail
ip=::::test:ens3:dhcp:1000:54:52:00:ab:cd:ef     MTU:fail  MAC:fail
ip=::::test:ens3:dhcp:1000:[54:52:00:ab:cd:ef]   MTU:fail  MAC:fail

("fail" means that MTU or MAC wasn't set according to the ip= parameter)

Version-Release number of selected component (if applicable):
dracut-033-353.el7

How reproducible:
always

Steps to Reproduce:
1. try to set MAC/MTU using the examples above

Actual results:
MAC/MTU is not set

Expected results:
MAC/MTU is set correctly

Additional info:
Comment 4 Jan Stodola 2016-08-11 08:25:45 UTC 
Retested with dracut-033-450.el7, all the following test cases work as expected:

ip=ens3:dhcp:1000                       MTU:OK    MAC:N/A
ip=ens3:dhcp::54:52:00:ab:cd:ef         MTU:N/A   MAC:OK
ip=ens3:dhcp::[54:52:00:ab:cd:ef]       MTU:N/A   MAC:OK
ip=ens3:dhcp:1000:54:52:00:ab:cd:ef     MTU:OK    MAC:OK
ip=ens3:dhcp:1000:[54:52:00:ab:cd:ef]   MTU:OK    MAC:OK

ip=::::test:ens3:dhcp:1000                       MTU:OK    MAC:N/A
ip=::::test:ens3:dhcp::54:52:00:ab:cd:ef         MTU:N/A   MAC:OK
ip=::::test:ens3:dhcp::[54:52:00:ab:cd:ef]       MTU:N/A   MAC:OK
ip=::::test:ens3:dhcp:1000:54:52:00:ab:cd:ef     MTU:OK    MAC:OK
ip=::::test:ens3:dhcp:1000:[54:52:00:ab:cd:ef]   MTU:OK    MAC:OK

ip=192.168.122.20::192.168.122.1:24:test:ens3:none:1000                      MTU:OK    MAC:N/A
ip=192.168.122.20::192.168.122.1:24:test:ens3:none::54:52:00:ab:cd:ef        MTU:N/A   MAC:OK
ip=192.168.122.20::192.168.122.1:24:test:ens3:none::[54:52:00:ab:cd:ef]      MTU:N/A   MAC:OK
ip=192.168.122.20::192.168.122.1:24:test:ens3:none:1000:54:52:00:ab:cd:ef    MTU:OK    MAC:OK
ip=192.168.122.20::192.168.122.1:24:test:ens3:none:1000:[54:52:00:ab:cd:ef]  MTU:OK    MAC:OK

Moving to VERIFIED.
Comment 7 errata-xmlrpc 2016-11-04 07:59:24 UTC 
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://rhn.redhat.com/errata/RHBA-2016-2530.html
Note You need to log in before you can comment on or make changes to this bug.