Bug 959803

Summary: wicked - unable to set MTU on root device
Product: [openSUSE] openSUSE Distribution Reporter: Per Jessen <per>
Component: NetworkAssignee: wicked maintainers <wicked-maintainers>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: bwiedemann, forgotten_lNYeazqpWh, per, pwieczorkiewicz, trenn, wicked-maintainers
Version: Leap 42.1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Per Jessen 2015-12-19 16:21:21 UTC
Hardware:  taggart13, zattoo box.
Software:  Leap42.1 plus updates

The system is booting over iSCSI, iBFT disabled.
I am unable to make wicked set MTU 9000 for the network device used for root. It ignores my MTU=9000 in /etc/sysconfig/network/ifcfg-eth1.  I have also tried with iBFT enabled (/etc/sysconfig/network/ifcfg-ibft0), same result. 

Setting it manually works fine:

# ip link set mtu 9000 dev eth1
# ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:30:48:90:80:d1 brd ff:ff:ff:ff:ff:ff
    inet 10.42.8.6/21 brd 10.42.15.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::230:48ff:fe90:80d1/64 scope link
       valid_lft forever preferred_lft forever
Comment 1 Bernhard Wiedemann 2015-12-20 06:07:39 UTC
I guess in this case, the dracut-built initrd would bring up the network
so maybe that operates differently from the normal wicked?
Comment 2 Per Jessen 2015-12-20 09:49:00 UTC
(In reply to Bernhard Wiedemann from comment #1)
> I guess in this case, the dracut-built initrd would bring up the network
> so maybe that operates differently from the normal wicked?

I'm not sure how the initrd interacts with the root network device. The network interface is already running when the initrd is loaded.
Comment 3 Pawel Wieczorkiewicz 2016-01-12 17:16:05 UTC
AFAICS the MTU and LLADDR setting works only for static ip interface configurations. It's been omitted for dhcp cases.
You use DHCP config for iSCSI root device I guess (not the dracut's ip= and root=iscsi: config)?

Could you please test if the fix applied to version in project [1] works for you?
Please update ifcfg file with new MTU value. Re-generate initrd by calling mkinitrd and reboot.
In case of problems you may specify rd.debug (and/or rd.break=cleanup) on boot command line in order to inspect what went wrong.

[1] https://build.opensuse.org/package/show/home:pwieczorkiewicz:branches:openSUSE:Leap:42.1:Update/dracut

Note: It's not wicked related bug.
Note2: The ifcfg-ibft* files must not be created. They usually are ignored, but may lead (might have led?) to problems due to YaST bugs (not sure whether they are fixed now). Furthermore in case of dracut the iBFT is (in older versions) handled by iscsistart -b reading info directly from the kernel interface.
Comment 4 Per Jessen 2016-01-13 07:24:52 UTC
(In reply to Pawel Wieczorkiewicz from comment #3)
> AFAICS the MTU and LLADDR setting works only for static ip interface
> configurations. It's been omitted for dhcp cases.
> You use DHCP config for iSCSI root device I guess (not the dracut's ip= and
> root=iscsi: config)?

Correct, I'm using DHCP.

> Could you please test if the fix applied to version in project [1] works for
> you?
> Please update ifcfg file with new MTU value. Re-generate initrd by calling
> mkinitrd and reboot.
> In case of problems you may specify rd.debug (and/or rd.break=cleanup) on
> boot command line in order to inspect what went wrong.
> 
> [1]
> https://build.opensuse.org/package/show/home:pwieczorkiewicz:branches:
> openSUSE:Leap:42.1:Update/dracut

Okay, I'll try it out.

> Note: It's not wicked related bug.

Okay, I couldn't think of who else might be responsible :-)

> Note2: The ifcfg-ibft* files must not be created. 

I'm booting iPXE with "sanboot --no-describe" so there is no iBFT.

> They usually are ignored, but may lead (might have led?) to problems due to
> YaST bugs (not sure whether they are fixed now). 

Yes, iBFT was a problem because the interface got renamed to ibft0 which screwed up things later on.  Andrei Borzenkov advised me of the "sanboot --no-describe" option.
Comment 5 Bernhard Wiedemann 2016-01-13 16:00:16 UTC
This is an autogenerated message for OBS integration:
This bug (959803) was mentioned in
https://build.opensuse.org/request/show/353427 42.1 / dracut
Comment 9 Pawel Wieczorkiewicz 2016-01-14 10:42:05 UTC
The fix has been verified positively. Submitted to SLE-12-SP1:Update and thereby should reach Leap too.
Comment 11 Per Jessen 2016-02-07 20:45:36 UTC
(In reply to Pawel Wieczorkiewicz from comment #9)
> The fix has been verified positively. Submitted to SLE-12-SP1:Update and
> thereby should reach Leap too.

Any idea when it is likely to hit Leap 42?
Comment 13 Swamp Workflow Management 2016-08-04 15:11:08 UTC
SUSE-RU-2016:1954-1: An update that has three recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 951003,959803,975959
CVE References: 
Sources used:
SUSE Linux Enterprise Server 12-SP1 (src):    dracut-037-72.1
SUSE Linux Enterprise Desktop 12-SP1 (src):    dracut-037-72.1
Comment 14 Swamp Workflow Management 2016-08-11 15:20:29 UTC
openSUSE-RU-2016:2044-1: An update that has three recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 951003,959803,975959
CVE References: 
Sources used:
openSUSE Leap 42.1 (src):    dracut-037-71.1
Comment 19 Swamp Workflow Management 2017-10-10 19:12:05 UTC
SUSE-SU-2017:2696-1: An update that solves one vulnerability and has 11 fixes is now available.

Category: security (moderate)
Bug References: 1005410,1006118,1007925,1008340,1008648,1017695,1032576,1035743,935320,959803,986734,986838
CVE References: CVE-2016-8637
Sources used:
SUSE Linux Enterprise Server 12-LTSS (src):    dracut-037-51.31.1