sysconfig mtu settings do not work correctly
Bug #1706973 reported by
Scott Moser
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Expired
|
Medium
|
Unassigned | ||
| curtin |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
Curtin's tests that derive from CentosTestNetwo
That can be reproduced in curtin's vmtest with:
./tools/
or more directly
./tools/
tests/
tests/
| 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 |
| description: | updated |
Revision history for this message
| Ryan Harper (raharper) wrote | #1 |
Revision history for this message
| James Falcon (falcojr) wrote | #2 |
| Changed in cloud-init: | |
| status: | Confirmed → Expired |
To post a comment you must log in.
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.