Merge pull request #95449 from wgabor0427/OSDOCS-15111

OSDOCS-15111 created z-stream release notes for 4.19.2

Author: stevsmit

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

@@ -2813,6 +2813,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.19.2
+[id="ocp-4-19-2_{context}"]
+=== RHSA-2025:9750 - {product-title} {product-version}.2 image release, bug fix, and security update advisory
+
+Issued: 01 July 2025
+
+{product-title} release {product-version}.2, which includes security updates, 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:9750[RHSA-2025:9750] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHSA-2025:9751[RHSA-2025:9751] 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.19.2 --pullspecs
+----
+
+[id="ocp-4-19-2-bug-fixes_{context}"]
+==== Bug fixes
+
+* Previously, the installation program checked only the first compute machine pool entry in the install configuration to determine whether to disable the Machine Config Operator (MCO) boot image management feature. If multiple compute pools were specified ({aws-first} edge nodes are the only supported scenario), but another compute machine pool had a custom Amazon Machine Image (AMI), the installation program would not disable the MCO boot image management and the custom AMI would be overwritten by the MCO. With this release, the installation program checks all compute machine pool entries and if a custom image is found, the MCO boot image management is disabled. (link:https://issues.redhat.com/browse/OCPBUGS-58060[OCPBUGS-58060])
+
+* Previously, if a user specified a custom boot image for {aws-first} or the {gcp-first}, the Machine Config Operator (MCO) would overwrite it with the default boot image during installation. With this release, a manifest generation was added for MCO configuration which disables the default boot image during installation if a custom image is specified. (link:https://issues.redhat.com/browse/OCPBUGS-57796[OCPBUGS-57796])
+
+* Previously, a validation issue within `oc-mirror` plugin caused the command to reject the `file://.` reference. Users attempting to use `file://.` for a content path received an error message stating `content filepath is tainted`. With this release, the `oc-mirror` plugin properly validates the '.' directory reference. (link:https://issues.redhat.com/browse/OCPBUGS-57786[OCPBUGS-57786])
+
+* Previously, the `oc-mirror v2` command was not using the correct filtered catalog during its operations, which led to errors such as including more operators than specified in the configuration, and trying to connect to the catalog registry during disk-to-mirror workflows even in air-gapped environments. With this release, the correct filtered catalog is used. (link:https://issues.redhat.com/browse/OCPBUGS-57784[OCPBUGS-57784])
+
+* Previously, the {ols-official} UI would disappear when the *Create Project* modal was opened or when modals on the Networking pages were triggered. This was due to the modals using the `useModal` hook causing the modals to overwrite each other. With this release, the modals no longer overwrite each other allowing multiple UI elements to be displayed simultaneously. (link:https://issues.redhat.com/browse/OCPBUGS-57755[OCPBUGS-57755])
+
+* Previously, the HAProxy configuration used the `/version` endpoint for health checks causing unreliable health checks to be generated. With this release, the liveness probe is customized to use `/livez?exclude=etcd&exclude=log` on IBM Cloud for more accurate health checks avoiding disruptions due to inappropriate probe configurations on Hypershift, while retaining `/version` for other platforms. (link:https://issues.redhat.com/browse/OCPBUGS-57485[OCPBUGS-57485])
+
+* Previously, the installer failed when AWS credentials were not found and the survey was attempting AWS regions preventing users from creating the `install-config` file. With this release, the installer no longer fails when AWS credentials are not set, allowing users to input them during the survey. (link:https://issues.redhat.com/browse/OCPBUGS-57394[OCPBUGS-57394])
+
+* Previously, cloning a persistent volume claim (PVC) in the web console resulted in an error due to an unsupported unit *B* for storage size. Because of this, users encountered errors when cloning the Red Hat OpenShift console PVC due to incorrect parsing of the storage size unit. With this release, support for *B* as unit of storage size has been removed from the Red{nbsp}Hat OpenShift console PVC. (link:https://issues.redhat.com/browse/OCPBUGS-57391[OCPBUGS-57391])
+
+* Previously, {olmv1-first} was used to install Operators with the `olm.maxOpenShiftVersion` set to  `4.19`.  Due to an issue with the {olmv1} parsing logic for floating-point formatted `olm.maxOpenShiftVersion`values, the system failed to prevent upgrades to {product-title}. With this release, the parsing logic for  `olm.maxOpenShiftVersion` has been corrected preventing upgrades to {product-title} when Operators with `olm.maxOpenShiftVersion:4.19` are installed. (link:https://issues.redhat.com/browse/OCPBUGS-56852[OCPBUGS-56852])
+
+
+* Previously, one of the `keepalived` health check scripts was failing due to missing permissions. This could result in the incorrect assignment of the ingress Virtual IP Address (VIP) in environments using shared ingress services.  With this release, the necessary permission was added back to the container so the health check now works correctly.  (link:https://issues.redhat.com/browse/OCPBUGS-56623[OCPBUGS-56623])
+
+
+[id="ocp-4-19-2-updating_{context}"]
+==== Updating
+To update an {product-title} 4.19 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.19.1
 [id="ocp-4-19-1_{context}"]
 === RHSA-2025:9278 - {product-title} {product-version}.1 image release, bug fix, and security update advisory