-
Spike
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
Impact statement for the OCPBUGS-57179 series:
Which 4.y.z to 4.y'.z' updates increase vulnerability?
- any to 4.18.z
Which types of clusters?
- A cluster gets impacted if it has assigned EgressIPs which can be verified by the PromQL query on the cluster count(ovnkube_clustermanager_num_egress_ips) > 0
What is the impact? Is it serious enough to warrant removing update recommendations?
- EgressIP functionality may fail if a pod IP is reused
How involved is remediation?
- SSH into each Node and run a command to either clear all the databases or clear the OVN constructs that are causing the issue. We recommend detection then flushing the OVN DBs. SeeĀ https://access.redhat.com/solutions/7125049 for details.
Is this a regression?
- yes
- blocks
-
OCPBUGS-57179 [4.20][upgrade] OCP4.18.X - Stale SNATs/LRPs due to failed sync to add metadata after upgrade
-
- Verified
-
- links to