-
Spike
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
-
False
-
-
False
-
None
-
1
-
None
-
CORENET Sprint 277, CORENET Sprint 278
An impact statement for the OCPBUGS-57354 bug.
Which 4.y.z to 4.y'.z' updates increase vulnerability?
- Updates from 4.16 (until OCPBUGS-57354 lands in a 4.16.z) to 4.17.
Which types of clusters?
- Clusters in the middle of an SDN-to-OVN migration.
What is the impact? Is it serious enough to warrant removing update recommendations?
- The update gets stuck.
How involved is remediation?
- No supported remediation is currently known.
Is this a regression?
- Yes and no. Updating to 4.17 while the SDN-to-OVN migration is in progress has never worked. However, updating from 4.y to 4.(y+1) is expected to work.
- is related to
-
OCPBUGS-57354 OCP4.16.z: It is possible to accidentally trigger an upgrade to 4.17 during a migration from SDN --> OVN leading to soft-lock state
-
- POST
-