OSDOCS-13316: Documented the 4.15.45 z-stream notes

Author: dfitzmau

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

@@ -2777,6 +2777,36 @@ 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.15.45
+[id="ocp-4-15-45_{context}"]
+=== RHSA-2025:1128 - {product-title} 4.15.45 bug fix and security update
+
+Issued: 12 February 2025
+
+{product-title} release 4.15.45, which includes security updates, is now available. The list of bug fixes that are included in this update is documented in the link:https://access.redhat.com/errata/RHSA-2025:1128[RHSA-2025:1128] advisory. The RPM packages that are included in this update are provided by the link:https://access.redhat.com/errata/RHSA-2025:1130[RHSA-2025:1130] 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.15.45 --pullspecs
+----
+
+[id="ocp-4-15-45-bug-fixes_{context}"]
+==== Bug fixes
+
+* Previously, crun failed to stop a container if you opened a terminal session and then disconnected from it. With this release, the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-48751[*OCPBUGS-48751*])
+
+* Previously, every time a subcription was reconciled, the OLM catalog Operator requested a full view of the catalog metadata from the catalog source pod of the subscription. These requests caused performance issues for the catalog pods. With this release, the OLM catalog Operator now uses a local cache that is refreshed periodically and reused by all subscription reconciliations, so that the performance issue for the catalog pods no longer persists. (link:https://issues.redhat.com/browse/OCPBUGS-48697[*OCPBUGS-48697*])
+
+* 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-48592[*OCPBUGS-48592*])
+
+[id="ocp-4-15-45-updating_{context}"]
+==== Updating
+To update an {product-title} 4.15 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.15.44
 [id="ocp-4-15-44_{context}"]
 === RHSA-2025:0646 - {product-title} 4.15.44 bug fix and security update
@@ -3503,7 +3533,7 @@ The following enhancement is included in this z-stream release:
 
 * Previously, the Ingress Operator could not successfully update the canary route because the Operator did not have permission to update `spec.host` or `spec.subdomain` on an existing route. With this release, the required permission is added to the cluster role for the Operator's `ServiceAccount` and the Ingress Operator can update the canary route. (link:https://issues.redhat.com/browse/OCPBUGS-36466[*OCPBUGS-36466*])
 
-* Previously, installing an Operator could sometimes fail if the same Operator had been previously installed and uninstalled. This was due to a caching issue. This bug fix updates {olm} to correctly install the Operator in this scenario, and as a result this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-36451[*OCPBUGS-36451*])
+* Previously, installing an Operator could sometimes fail if the same Operator had been previously installed and uninstalled. This was due to a caching issue. This bug fix updates Operator Lifecycle Manager (OLM) to correctly install the Operator in this scenario, and as a result this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-36451[*OCPBUGS-36451*])
 
 * Previously, after installing the Pipelines Operator, Pipeline templates took some time to become available in the cluster, but users were still able to create the Deployment. With this update, the *Create* button on the *Import from Git* page is disabled if there is no pipeline template present for the resource selected. (link:https://issues.redhat.com/browse/OCPBUGS-34477[*OCPBUGS-34477*])