Which 4.y.z to 4.y'.z' updates increase vulnerability?

• Customers upgrading from any 4.y to 4.17.16, 4.17.17, 4.17.18, 4.17.19, and potentially later versions. To view the fixed version, see the details of OCPBUGS-51339.

Which types of clusters?

• HostedControlPlanes Managed (ROSA/ARO) and Self-Managed. Classic/standalone clusters are not exposed.

What is the impact? Is it serious enough to warrant removing update recommendations?

• Once you trigger an upgrade to one of the affected versions, the HostedCluster will stay in "Progressing" state, even if the cluster nodes are upgraded (status.conditions[.type="Progressing"].status). This is because of a discrepancy between the reported version from CVO and the OCP version set in the spec. The rest of the update will complete, and new component versions will roll out. This regression only impacts the status of the Progressing condition, but it could block future MachineConfig changes from being applied to the NodePools, and by extension, to the worker nodes of the HostedCluster.

How involved is remediation?

• The remediation consist in an upgrade to a higher z version, which contains the patch when this release got delivered.

Is this a regression?

• No, this error was introduced by a feature.