-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.16
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.
- blocks
-
OCPBUGS-41255 Configure-ovs doesn't persist ethtool configuration
- Closed
- is cloned by
-
OCPBUGS-41255 Configure-ovs doesn't persist ethtool configuration
- Closed
- is duplicated by
-
OCPBUGS-37538 [RHOCP 4.16] cluster operators are getting degraded in fresh installation
- Closed
- is related to
-
OCPBUGS-25312 [OVN][IPSEC EW]Upgrade from 4.14->4.15 failed for Vsphere
- Closed
- relates to
-
OCPBUGS-42973 Customer needs source ID active/active bonding XOR (mode 2)
- Closed
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update