-
Bug
-
Resolution: Done
-
Undefined
-
4.13.z, 4.12.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
3
-
None
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 266
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
In the "Configuring an additional network" documentation, the "Configuration for a MACVLAN additional network" section shows the `mtu` value to be a String, however this fails when used and this works when it's configured as an integer.
Table 6, "MACVLAN CNI plugin JSON configuration object", states that the value for the key "mtu" needs to be a string. This is incorrect, as this value needs to be an integer.
Settings this value as a string causes pods using this additional network to become unschedulable.
This value is also shown in the CNI specification as an integer here:
https://github.com/containernetworking/cni/blob/main/SPEC.md#add-success
https://www.cni.dev/plugins/v1.0/main/macvlan/
Reading the CNI spec reference, this indicates that all of the MTU fields might need to be reviewed/changed to Integer.
Version-Release number of selected component (if applicable):
https://docs.openshift.com/container-platform/4.14/networking/multiple_networks/configuring-additional-network.html#nw-multus-macvlan-object_configuring-additional-network
How reproducible:
Steps to Reproduce:
1. Follow the instructions in the documentation for setting the MTU for MACVLAN configuration.
Actual results:
The Pods start failing to schedule if a String is used. (following the documentation)
Expected results:
Following the documentation sets the MTU correctly.
Additional info:
- links to