Red Hat Bugzilla – Bug 1271656
MTU/MAC not set in dracut
Last modified: 2017-02-09 03:56:07 EST
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:
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.
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