sysconfig mtu settings do not work correctly

Bug #1706973 reported by Scott Moser on 2017-07-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Unassigned
curtin
Medium
Unassigned

Bug Description

Curtin's tests that derive from CentosTestNetworkMtuAbs (Centos66TestNetworkMtu and Centos70TestNetworkMtu) are currently not working.

That can be reproduced in curtin's vmtest with:
  ./tools/jenkins-runner -p4 tests/vmtests/test_metwork_mtu

or more directly
  ./tools/jenkins-runner \
     tests/vmtests/test_network_mtu.py:Centos66TestNetworkMtu \
     tests/vmtests/test_network_mtu.py:Centos70TestNetworkMtu

Scott Moser (smoser) on 2017-07-27
Changed in cloud-init:
status: New → Confirmed
Changed in curtin:
status: New → Confirmed
Changed in cloud-init:
importance: Undecided → Medium
Changed in curtin:
importance: Undecided → Medium
Scott Moser (smoser) on 2017-07-27
description: updated
Ryan Harper (raharper) wrote :

In particular, this tests covers setting different MTUs for interfaces which may have IPV6 configurations which need an IPV6_MTU setting; while IPV6_MTU is supported, if the IPV6_MTU value is higher than the device MTU, the IPV6_MTU setting won't be value (the device will break up the v6 packets at the lower MTU). In Ubuntu, there's some additional logic added to raise the underlying device MTU to match the IPV6_MTU. This logic is not present in sysconfig scripts at this time.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers