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

Kuryr uses default MTU for service network

XMLWordPrintable

    • -
    • Moderate
    • None
    • 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 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:

       

              mdulko Michał Dulko (Inactive)
              mdulko Michał Dulko (Inactive)
              Ramón Lobillo Ramón Lobillo
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: