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

Kuryr uses default MTU for service network

    XMLWordPrintable

Details

    • -
    • Moderate
    • ShiftStack Sprint 224, ShiftStack Sprint 225, ShiftStack Sprint 226, ShiftStack Sprint 227, ShiftStack Sprint 228, ShiftStack Sprint 229
    • 6
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: CNO was ignoring Kuryr MTU settings when creating neutron network for OpenShift Services.
      Consequence: Network was created with default MTU, which may have been incompatible with what the cluster admin intended.
      Fix: Configured MTU is now taken into account.
      Result: Service neutron network is created with configured MTU.
      Show
      Cause: CNO was ignoring Kuryr MTU settings when creating neutron network for OpenShift Services. Consequence: Network was created with default MTU, which may have been incompatible with what the cluster admin intended. Fix: Configured MTU is now taken into account. Result: Service neutron network is created with configured MTU.
    • Bug Fix
    • Proposed
    • Administer

    Description

      Description of problem:

      In CNO Kuryr bootstrap creates network for Services. The problem is that we don't specify MTU there and use the default. We should use MTU of the nodes network instead.

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

      4.8

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create cluster with Kuryr and custom MTU.
2. Check MTU version of the kuryr-service-network

      Actual results:

      It has cluster's default MTU

      Expected results:

      Should have nodes network MTU

      Additional info:

       

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-4896 Kuryr uses default MTU for service network

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1632 Kuryr uses default MTU for service network

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-4896 Kuryr uses default MTU for service network

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-4898 Kuryr uses default MTU for service network

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/cluster-network-operator#1545: Bug: OCPBUGS-736: Kuryr: Use machine net MTU to create service net

          GitHub openshift/cluster-network-operator#1586: Bug OCPBUGS-736: Kuryr: If set use MTU from Config for svc net

          Activity

            People

              mdulko Michał Dulko
              mdulko Michał Dulko
              Ramón Lobillo Ramón Lobillo
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: