-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.13.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
CNF Network Sprint 247, CNF Network Sprint 248, CNF Network Sprint 249, CNF Network Sprint 250, CNF Network Sprint 251
-
5
-
In Progress
-
Release Note Not Required
-
This issue only affects 4.14 and 4.13 releases
-
None
-
None
-
None
-
None
Description of problem:
When doing EUS upgrade, our docs gave an example that the user could choose to upgrade master nodes, then upgrade the operator and lastly upgrade worker nodes. This doesn't apply for the sriov operator. More details are in https://redhat-internal.slack.com/archives/CQEK2R890/p1704179627915889
Version-Release number of selected component (if applicable):
4.14
How reproducible:
100%
Work progress tracking
sriov-cni | ib-sriov-cni | sriov-network-operator | ||
---|---|---|---|---|
upstream | ![]() |
![]() ![]() |
![]() |
|
ocp 4.16 downstream merge | ![]() |
![]() |
![]() |
|
implement RHEL8/9 conditional copy | ![]() |
![]() |
— | |
ocp 4.15 backport | ![]() |
![]() |
https://github.com/openshift/sriov-network-operator/pull/893 ![]() |
|
ocp 4.14 backport - | ||||
ocp 4.13 backport conditional copy |
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- links to
-
RHEA-2024:0040 OpenShift Container Platform 4.16.z extras update
(3 links to)