OSDOCS-13591: Documented 4.17.20 z-stream release notes

Author: dfitzmau

release_notes/ocp-4-17-release-notes.adoc

@@ -2879,6 +2879,44 @@ This section will continue to be updated over time to provide notes on enhanceme
 For any {product-title} release, always review the instructions on xref:../updating/updating_a_cluster/updating-cluster-web-console.adoc#updating-cluster-web-console[updating your cluster] properly.
 ====
 
+// 4.17.20
+[id="ocp-4-17-20_{context}"]
+=== RHSA-2025:2445 - {product-title} {product-version}.20 bug fix, and security update advisory
+
+Issued: 12 March 2025
+
+{product-title} release {product-version}.20 is now available. The list of bug fixes that are included in the update is documented in the link:https://access.redhat.com/errata/RHSA-2025:2445[RHSA-2025:2445] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:2447[RHBA-2025:2447] advisory.
+
+Space precluded documenting all of the container images for this release in the advisory.
+
+You can view the container images in this release by running the following command:
+
+[source,terminal]
+----
+$ oc adm release info 4.17.20 --pullspecs
+----
+
+[id="ocp-4-17-20-bug-fixes_{context}"]
+==== Bug fixes
+
+* Previously, Local Storage Operator (LSO) ignored existing Small Computer System Interface (SCSI) symlinks during persistent volumes (PV) creation. With this release, the LSO no longer ignores these symlinks because it gathers these symlinks before finding new symlinks when creating a PV. (link:https://issues.redhat.com/browse/OCPBUGS-51291[*OCPBUGS-51291*])
+
+* Previously, when the OVN-Kubernetes network plugin and the Kubernetes-NMState Operator interacted with each other, unexpected connection profiles persisted on disk storage. These connection profiles sometimes caused the `ovs-configuration` service to fail when restarted. With this release, the unnecessary connection profiles are now cleaned before the `ovs-configuration` starts so that this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-52257[*OCPBUGS-52257*])
+
+* Previously, the `vmware-vsphere-csi-driver-operator` Container Storage Interface (CSI) driver entered panic mode when the {vmw-full} vCenter address was incorrect or missing. With this release, the CSI driver does not go into panic mode if the {vmw-full} vCenter address is incorrect or missing. (link:https://issues.redhat.com/browse/OCPBUGS-52207[*OCPBUGS-52207*])
+
+* Previously, the *Cluster Settings* page would not properly render during a cluster update if the `ClusterVersion` did not receive a `Completed` update.  With this release, the *Cluster Setting* page properly renders even if the `ClusterVersion` has not received a `Completed` update. (link:https://issues.redhat.com/browse/OCPBUGS-51292[*OCPBUGS-51292*])
+
+* Previously, the alerts links on the *Alert rules* page of the *Developer* perspective included external labels to invalid links. This happened because the URL for the *Alerts* page did not expect external labels. With this release, the external labels are no longer added to the alerts URL on the *Alert rules* page so the alerts links are accurate. (link:https://issues.redhat.com/browse/OCPBUGS-51126[*OCPBUGS-51126*])
+
+* Previously, for a `kubevirt-csi` pod that ran on a node in a hosted cluster, the persistent volume claim (PVC) from the hosted cluster was removed from the virtual machine (VM) after the VM was rebooted. However, the `VolumeAttachment` resource was not removed and this caused issues for the cluster as it expected the PVC to be attached to the VM. With this release, after a VM is rebooted, the `VolumeAttachment` resource is removed so that the cluster issues no longer occur. (link:https://issues.redhat.com/browse/OCPBUGS-44623[*OCPBUGS-44623*])
+
+* Previously, in bare-metal configurations where the provisioning network was disabled but the `bootstrapProvisioningIP` field was set, the bare-metal provisioning components would fail to start. These failures occur when the provisioning process reconfigures the external network interface on the bootstrap VM during the process of pulling container images. With this release, dependencies are added to ensure that interface reconfiguration only occurs when the network is idle, preventing conflicts with other processes. As a result, the bare-metal provisioning components now start reliably, even when the `bootstrapProvisioningIP` field is set and the provisioning network is disabled. (link:https://issues.redhat.com/browse/OCPBUGS-43528[*OCPBUGS-43528*])
+
+[id="ocp-4-17-20-updating_{context}"]
+==== Updating
+To update an {product-title} 4.17 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].
+
 // 4.17.19
 [id="ocp-4-17-19_{context}"]
 === RHSA-2025:1912 - {product-title} {product-version}.19 bug fix, and security update advisory