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

Configure-ovs doesn't persist ethtool configuration

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • Hide

      * Previously, bonds that were configured in `active-backup` mode would have IPsec Encapsulating Security Payload (ESP) offload active even if underlying links did not support ESP offload. This caused IPsec associations to fail. With this release, ESP offload is disabled for bonds so that IPsec associations pass. (link:https://issues.redhat.com/browse/OCPBUGS-41256[*OCPBUGS-41256*])
      --------
      Cause: bonds configured in active-backup mode would have ESP offload active even if underlying links didn't support it
      Consequence: IPSec associations fail
      Fix: disable ESP offload on bonds if underlying links don't support it
      Result: IPSec associations succeed
      Show
      * Previously, bonds that were configured in `active-backup` mode would have IPsec Encapsulating Security Payload (ESP) offload active even if underlying links did not support ESP offload. This caused IPsec associations to fail. With this release, ESP offload is disabled for bonds so that IPsec associations pass. (link: https://issues.redhat.com/browse/OCPBUGS-41256 [* OCPBUGS-41256 *]) -------- Cause: bonds configured in active-backup mode would have ESP offload active even if underlying links didn't support it Consequence: IPSec associations fail Fix: disable ESP offload on bonds if underlying links don't support it Result: IPSec associations succeed
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-41255. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-39438. The following is the description of the original issue:
      —
      Description of problem: If a customer applies ethtool configuration to the interface used in br-ex, that configuration will be dropped when br-ex is created. We need to read and apply the configuration from the interface to the phys0 connection profile, as described in https://issues.redhat.com/browse/RHEL-56741?focusedId=25465040&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25465040

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

      How reproducible: Always

      Steps to Reproduce:

      1. Deploy a cluster with an NMState config that sets the ethtool.feature.esp-tx-csum-hw-offload field to "off"

      2.

      3.

      Actual results: The ethtool setting is only applied to the interface profile which is disabled after configure-ovs runs

      Expected results: The ethtool setting is present on the configure-ovs-created profile

      Additional info:

      Affected Platforms: VSphere. Probably baremetal too and possibly others.

              bnemec@redhat.com Benjamin Nemec
              openshift-crt-jira-prow OpenShift Prow Bot
              Ross Brattain Ross Brattain
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: