Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-37343

Change MTU process using the NetworkManager method doesn't work as expected.

XMLWordPrintable

    • Important
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Following the documentation for Changing cluster MTU,] the section related to the Network Manager method didn't affect the node:

      $ cat /etc/NetworkManager/conf.d/99-ens192-mtu.conf
[connection-ens192-mtu]
match-device=interface-name:ens192
ethernet.mtu=1470 

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether 00:50:56:8f:40:b0 brd ff:ff:ff:ff:ff:ff
    altname enp11s0

      I tried with a different value (1510) but it didn't change. However, I tried the same using a 4.14.25 cluster and it worked correctly:

      NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.14.25   True        False         55d     Cluster version is 4.14.25

$ cat /etc/NetworkManager/conf.d/99-ens192-mtu.conf [connection-ens192-mtu]
match-device=interface-name:ens192
ethernet.mtu=1470

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1470 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether 00:50:56:8f:a4:63 brd ff:ff:ff:ff:ff:ff
    altname enp11s0

       

       

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

      1. Follow the steps from documentation using the NetworkManager approach.

      2. Once the changes are applied using machine-config, check that mtu is changed in the main physical interface.

      3.

      Actual results: The mtu didn't change.

      Expected results: Mtu should change to the specified value.

       

            sdn-team-bot sdn-team bot
            rhn-gps-alfredo Alfredo Pizarro
            Anurag Saxena Anurag Saxena
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: