Merge pull request #87191 from dfitzmau/OSDOCS-13129

OSDOCS-13129: Documented the 4.16.32 z-stream RNs

Author: dfitzmau

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

@@ -3347,6 +3347,52 @@ 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.16.32
+[id="ocp-4-16-32_{context}"]
+=== RHSA-2025:0650 - {product-title} {product-version}.32 bug fix and security update
+
+Issued: 29 January 2025
+
+{product-title} release {product-version}.32 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:0650[RHSA-2025:0650] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:0652[RHBA-2025:0652] 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.16.32 --pullspecs
+----
+
+[id="ocp-4-16-32-bug-fixes_{context}"]
+==== Bug fixes
+
+* Previously, the {olm-first} would sometimes concurrently resolve the same namespace in a cluster. This led to subscriptions reaching a terminal state of `ConstraintsNotSatisfiable`, because two concurrent processes interacted with a subscription and this caused a CSV file to become unassociated. With this release, {olm} no longer concurrently resolves namespaces, so that {olm} correctly processes a subscription without leaving a CSV file in an unassociated state. (link:https://issues.redhat.com/browse/OCPBUGS-48661[*OCPBUGS-48661*])
+
+* Previously, {gcp-first} updated their zone API error message, and this update caused the {product-title} machine controller to mistakenly label a machine as valid because of a generated temporary error message that was related to {gcp-first}. This situation prevented invalid machines transitioning into a failed state. With this release, the machine controller now handles the error correctly by checking if an invalid zone or `projectID` exists in the machine configuration. The machine controller then correctly places the machine in a failed state. (link:https://issues.redhat.com/browse/OCPBUGS-48484[*OCPBUGS-48484*])
+
+* Previously, if the `RendezvousIP` matched a substring in the `next-hop-address` field of a compute node configuration, a validation error. The `RendezvousIP` must match only a control plane host address. With this release, a substring comparison for `RendezvousIP` is used only against a control plane host address, so that the error no longer exists. (link:https://issues.redhat.com/browse/OCPBUGS-48442[*OCPBUGS-48442*])
+
+// SME review
+* Previously, you could not use all the available machine types in a zone for a cluster installed on {ibm-power-server-name}. This issues existed because all zones in a region were assumed to have the same set of machine types. With this release, you can use all the available machine types in a zone for a cluster installed on {ibm-power-server-name}. (link:https://issues.redhat.com/browse/OCPBUGS-47663[*OCPBUGS-47663*])
+
+* Previously, a `PipelineRuns` CR that used a resolver could not be rerun on the {product-title} web console. If you attempted ro rerun the CR, a `Invalid PipelineRun configuration, unable to start Pipeline.` was generated. With this release, you can now rerun a `PipelineRuns` CR that uses resolver without experience this issue. (link:https://issues.redhat.com/browse/OCPBUGS-46602[*OCPBUGS-46602*]) 
+
+* Previously, when you used the *Form View* to edit `Deployment` or `DeploymentConfig` API objects on the {product-title} web console, duplicate `ImagePullSecrets` parameters existed in the YAML configuration for either object. With this release, a fix ensures that duplicate `ImagePullSecrets` parameters do not get automatically added for either object. (link:https://issues.redhat.com/browse/OCPBUGS-45948[*OCPBUGS-45948*])
+
+* Previously, when the installation program installed a cluster on {azure-first}, the installation program enabled cross-tenant objects and replicated them. These replicated objects do not comply with Payment Card Industry Data Security Standard (PCI DSS) and the Federal Financial Supervisory Authority ( BaFin ) regulations. With this release, the installation program disables the objects, so that the cluster stricly adheres to the previously mentioned data governance regulations. (link:https://issues.redhat.com/browse/OCPBUGS-45999[*OCPBUGS-45999*])
+
+* Previously, {op-system-base-full} CoreOS templates that were shipped by the  Machine Config Operator (MCO) caused node scaling to fail on {rh-openstack-first}. This issue happened because of an issue with `systemd` and the presence of a legacy boot image from older versions of {product-title}. With this release, a patch fixes the issue with `systemd` and removes the legacy boot image, so that node scaling can continue as expected. (link:https://issues.redhat.com/browse/OCPBUGS-43765[*OCPBUGS-43765*])
+
+* Previously, on the {product-title} web console, the {vmw-full} configuration dialog box stalled because of network or validation errors. With this release, a fix ensures that you can close the dialog, cancel any configuration changes, or edit a configuration without the errors causing the dialog to stall. (link:https://issues.redhat.com/browse/OCPBUGS-29823[*OCPBUGS-29823*])
+
+* Previously on the {product-title} web console, the {vmw-full} configuration dialog box did not validate values entered into any fields because of an issue with the {vmw-short} plugin. After you saved the configuration, the outputted data was not logically formatted. With this release, the {vmw-short} plugin now performs validation checks on inputted data so the plugin outputs the data in a logical format.(link:https://issues.redhat.com/browse/OCPBUGS-29616[*OCPBUGS-29616*])
+
+[id="ocp-4-16-32-updating_{context}"]
+==== Updating
+
+To update an existing {product-title} {product-version} cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster by using the CLI].
+
 // 4.16.30
 [id="ocp-4-16-30_{context}"]
 === RHSA-2025:0140 - {product-title} {product-version}.30 bug fix and security update
@@ -3369,13 +3415,13 @@ $ oc adm release info 4.16.30 --pullspecs
 
 * Previously, the Operator Lifecycle Manager (OLM)catalog registry pods were terminated by the kubelet with a `TerminationByKubelet` error, and the pods were not recreated by the catalog Operator. With this release, the registry pods are recreated without an error. (link:https://issues.redhat.com/browse/OCPBUGS-47738[*OCPBUGS-47738*])
 
- * Previously, the certificate signing request (CSR) approver included certificates from other systems in its calculations to determine if it was congested. When this happened, the CSR approver stopped approving certificates. With this release, the CSR approver only includes CSRs that it can approve, using the `signerName` property as a filter. The CSR approver only prevents new approvals when there are a large number of CSRs, for the `signerName` values that it observes, and for certificates that it does not approve. (link:https://issues.redhat.com/browse/OCPBUGS-47704[*OCPBUGS-47704*])
+* Previously, the certificate signing request (CSR) approver included certificates from other systems in its calculations to determine if it was congested. When this happened, the CSR approver stopped approving certificates. With this release, the CSR approver only includes CSRs that it can approve, using the `signerName` property as a filter. The CSR approver only prevents new approvals when there are a large number of CSRs, for the `signerName` values that it observes, and for certificates that it does not approve. (link:https://issues.redhat.com/browse/OCPBUGS-47704[*OCPBUGS-47704*])
 
- * Previously, the Performance Profile Creator (PPC) failed to build a performance profile for compute nodes that had different core ID numbering (core per socket) for their logical processors and the nodes existed under the same node pool. With this release, the PPC does not fail to create the performance profile because the PPC can build a performance profile for a cluster that has compute nodes with different core ID numbering for their logical processors. The PPC produces a warning message to use the generated performance profile with caution, because different core ID numbering might impact the system optimization and isolated management of tasks. (link:https://issues.redhat.com/browse/OCPBUGS-47701[*OCPBUGS-47701*])
+* Previously, the Performance Profile Creator (PPC) failed to build a performance profile for compute nodes that had different core ID numbering (core per socket) for their logical processors and the nodes existed under the same node pool. With this release, the PPC does not fail to create the performance profile because the PPC can build a performance profile for a cluster that has compute nodes with different core ID numbering for their logical processors. The PPC produces a warning message to use the generated performance profile with caution, because different core ID numbering might impact the system optimization and isolated management of tasks. (link:https://issues.redhat.com/browse/OCPBUGS-47701[*OCPBUGS-47701*])
 
- * Previously, an event was missed by the informer watch stream. If an object was deleted while this disconnection occurred, the informer resulted in a different type, reported that the state was invalid, and the object was deleted. With this release, the temporary disconnection possibilities are handled correctly. (link:https://issues.redhat.com/browse/OCPBUGS-47645[*OCPBUGS-47645*])
+* Previously, an event was missed by the informer watch stream. If an object was deleted while this disconnection occurred, the informer resulted in a different type, reported that the state was invalid, and the object was deleted. With this release, the temporary disconnection possibilities are handled correctly. (link:https://issues.redhat.com/browse/OCPBUGS-47645[*OCPBUGS-47645*])
 
- * Previously, when using the `SiteConfig` custom resource (CR) to delete a cluster or a node, the `BareMetalHost` CR was stuck in the `Deprovisioning` state. With this release, the order deletion is correct and the `SiteConfig` CR deletes a cluster or a node successfully. This fix requires version {gitops-title} 1.13 or later. (link:https://issues.redhat.com/browse/OCPBUGS-46524[*OCPBUGS-46524*])
+* Previously, when using the `SiteConfig` custom resource (CR) to delete a cluster or a node, the `BareMetalHost` CR was stuck in the `Deprovisioning` state. With this release, the order deletion is correct and the `SiteConfig` CR deletes a cluster or a node successfully. This fix requires version {gitops-title} 1.13 or later. (link:https://issues.redhat.com/browse/OCPBUGS-46524[*OCPBUGS-46524*])
 
 [id="ocp-4-16-30-updating_{context}"]
 ==== Updating