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

Kuryr uses default MTU for service network

XMLWordPrintable

    • -
    • Moderate
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, the Cluster Network Operator (CNO) configuration ignored Kuryr's maximum transmission unit (MTU) settings when using the {rh-openstack-first} Networking service (neutron) component to create a network for OpenShift services. CNO would create a network in Neutron with the wrong MTU property, and this action could cause incompatibility issues among network components that interact with a packet. With this update, the CNO does not ignore the Kuryr MTU setting when creating the network for services. You can then use the network to host OpenShift services.(link:https://issues.redhat.com/browse/OCPBUGS-4896[*OCPBUGS-4896*])
      Show
      Previously, the Cluster Network Operator (CNO) configuration ignored Kuryr's maximum transmission unit (MTU) settings when using the {rh-openstack-first} Networking service (neutron) component to create a network for OpenShift services. CNO would create a network in Neutron with the wrong MTU property, and this action could cause incompatibility issues among network components that interact with a packet. With this update, the CNO does not ignore the Kuryr MTU setting when creating the network for services. You can then use the network to host OpenShift services.(link: https://issues.redhat.com/browse/OCPBUGS-4896 [* OCPBUGS-4896 *])
    • Bug Fix
    • Done
    • Administer

      This is a clone of issue OCPBUGS-736. The following is the description of the original issue:

      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:

       

            Unassigned Unassigned
            openshift-crt-jira-prow OpenShift Prow Bot
            Ramón Lobillo Ramón Lobillo
            Darragh Fitzmaurice Darragh Fitzmaurice
            Red Hat Employee
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: