-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.13.z, 4.14.0, 4.15.0
-
No
-
False
-
This is a clone of issue OCPBUGS-19947. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-19818. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-18595. The following is the description of the original issue:
—
Description of problem:
RHCOS in 4.13 bumped to OVS 3.1, we should do the same for RHEL workers as the client side (SDN pods) may soon depend on 3.1 features and 3.1 is known to perfom better
Version-Release number of selected component (if applicable):
4.13.z, 4.14.0, 4.15.0
How reproducible:
100%
Steps to Reproduce:
1. Install OCP 4.13, 4.14, or 4.15 2. Add RHEL workers per https://docs.openshift.com/container-platform/4.13/machine_management/adding-rhel-compute.html
Actual results:
openvswitch2.17 is installed on RHEL workers while RHCOS workers have openvswitch3.1
Expected results:
All nodes use openvswitch3.1 on the host
Additional info:
While this may not cause issues currently, OVS 3.1 is known to perform better and clusters upgrading to OCP 4.15 will assume that all hosts have at least OVS 3.1 or later and may depend on 3.1 features to complete the upgrade.
- clones
-
OCPBUGS-19947 RHEL8 workers in 4.13+ should use openvswitch3.1
- Closed
- is blocked by
-
OCPBUGS-19947 RHEL8 workers in 4.13+ should use openvswitch3.1
- Closed
- links to
-
RHBA-2023:7823 OpenShift Container Platform 4.12.z bug fix update