Changing MTU to jumbo frame on Data network causes reboot cycling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Steven Webster |
Bug Description
Title
-----
Changing MTU value on Data network causes reboot cycling
Brief Description
-----------------
On Multinode Local storage configuration with data network, we should change MTU value from 1500 to 3000 on locked compute node. After performing Unlock action the compute reboots normally until the terminal shows the login console, starting with the reboot cycle.
Severity
--------
Major
Steps to Reproduce
------------------
description: change the mtu value of the data interface using cli
step-1: lock a compute node
step-2: use the system host-if-modify command to specify the interface and the new mtu value on the node
$ system host-if-modify -m 3000 compute-0 eth1000
step-3: unlock the node
step-4: repeat the above steps on each compute nodes
Expected Behavior
-----------------
The compute should be on unlock active state without issues
Actual Behavior
---------------
Compute node is rebooting as soon as console ask for password.
Las messages on dmesg shows:
[ 94.543418] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 105.314803] cgroup: new mount options do not match the existing superblock, will be ignored
[ 112.198930] watchdog watchdog0: watchdog did not stop!
[ 113.456691] nfsd: last server has exited, flushing export cache
[ 118.958720] device ovs-netdev left promiscuous mode
[ 120.218603] watchdog watchdog0: watchdog did not stop!
Reproducibility
---------------
100%
System Configuration
-------
Bare Metal Multinode Local Storage Configuration 2 controllers 2 computes
ISO
---
Tiemstamp/Logs
--------------
[ 94.543418] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 105.314803] cgroup: new mount options do not match the existing superblock, will be ignored
[ 112.198930] watchdog watchdog0: watchdog did not stop!
[ 113.456691] nfsd: last server has exited, flushing export cache
[ 118.958720] device ovs-netdev left promiscuous mode
[ 120.218603] watchdog watchdog0: watchdog did not stop!
/var/log/
The ovs-vswitchd.log shows |ERR| failed to create memory pool for netdev eth0 with MTU 3000 on socket 0: Invalid argument.
puppet.log shows
/Stage[
iso : stx-2018-
Branch/Pull Time/Commit
-------
stx-tools
Attaching dmesg output
description: | updated |
tags: | added: stx.networking |
Changed in starlingx: | |
assignee: | nobody → Steven Webster (swebster-wr) |
tags: |
added: stx.2019.05 removed: stx.2019.03 |
Changed in starlingx: | |
status: | Fix Committed → Fix Released |
tags: |
added: stx.2.0 removed: stx.2019.05 |
This is also visible in the following:
System Configuration ------- ------
-------
Bare Metal Multinode External (CEPH) Storage Configuration 2 controllers 2 computes 2 Storages (CEPH).
The signature of the failure is the same as described by @Elio.