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

[DOC] Correct checks in MTU migration procedures.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.14
    • Documentation / SDN
    • No
    • 3
    • OSDOCS Sprint 252, OSDOCS Sprint 253
    • 2
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      The documentation reporting to Change the cluster MTU here:
      - https://docs.openshift.com/container-platform/4.14/networking/changing-cluster-network-mtu.html#nw-cluster-mtu-change_changing-cluster-network-mtu
      
      Is reporting incorrect checks at point 8.b causing confusion to customer. 
      
      Checks are reporting:
      
      ~~~
      If the machine config is successfully deployed, the previous output contains the /etc/NetworkManager/system-connections/<connection_name> file path.
      
      The machine config must not contain the ExecStart=/usr/local/bin/mtu-migration.sh line.
      ~~~
      
      But the files to check in reality are "/etc/NetworkManager/conf.d/" and the "ExecStart=/usr/local/bin/mtu-migration.sh" is expected to be present at this stage, it is removed only after point 10.
      
      

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

      4.14 but probably all the supported releases.

            rhn-support-stevsmit Steven Smith
            rhn-support-cpassare Christian Passarelli
            Anurag Saxena Anurag Saxena
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: