-
Spike
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
False
-
None
-
False
-
---
-
-
-
0
-
0
Impact statement for the OCPBUGS-43454 series:
Which 4.y.z to 4.y'.z' updates increase vulnerability?
Customer using secondary OVN-Kubernetes networks of localnet topology without subnets upgrading from any 4.16 to any 4.17.
This is pretty much any virtualization customer using localnet secondary networks - since networks with subnets defined are not supported for virt workloads.
Which types of clusters?
All of them.
What is the impact? Is it serious enough to warrant removing update recommendations?
The upgrade will not finish successfully; newly added workloads will not be able to be created.
How involved is remediation?
Admin must remove all the workloads attached to all their localnet networks (without subnets), then remove all their localnet networks without subnets. Meaning, all the localnet topology networks in use for virtualization users must be removed, alongside the VMs connected to them.
is a regression?
Yes; introduced in 4.17.0 .
- relates to
-
OCPBUGS-43454 ovnkube-control-plane pods crash when upgrading from 4.16 to 4.17 with localnet topology networks without subnets
- POST