[OSDOCS#18502]: Modularization for 4.17.51 to 4.17.41 release notes

modules/zstream-4-17-41.adoc

@@ -0,0 +1,39 @@
+// Module included in the following assemblies:
+//
+// * release_notes/ocp-4-17-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ocp-4-17-41_{context}"]
+= RHSA-2025:17232 - {product-title} {product-version}.41 fixed issues and security update
+
+Issued: 08 October 2025
+
+[role="_abstract"]
+{product-title} release {product-version}.41 is now available. The list of fixed issues that are included in the update is documented in the link:https://access.redhat.com/errata/RHSA-2025:17232[RHSA-2025:17232] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:17230[RHBA-2025:17230] 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.41 --pullspecs
+----
+
+[id="ocp-4-17-41-fixed-issues_{context}"]
+== Fixed issues
+
+* Before this release, pods on the same node could not reach a pod's secondary `Localnet` interface on a `br-ex` bridge, so the pod defaulted to the primary network. With this release, communication between a `Localnet` pod and a pod running on the same node is possible, when the `Localnet` network's IP addresses are on the same subnet as the host network. (link:https://issues.redhat.com/browse/OCPBUGS-59381[OCPBUGS-59381])
+
+* Before this release, when the `configure-ovs.sh` script activated connection profiles, it triggered an error state on the switch side that caused ports to be disabled. With this release, the `configure-ovs.sh` script waits for normal activation to occur and does not change the profile states, unless it is necessary. This change prevents the link flapping that previously caused problems. (link:https://issues.redhat.com/browse/OCPBUGS-60890[OCPBUGS-60890])
+
+* Before this release, the `PrometheusRemoteWriteBehind` alerts could activate, even when the remote endpoint did not receive any data. With this release, these alerts do not activate when the remote endpoint does not received data. (link:https://issues.redhat.com/browse/OCPBUGS-61766[OCPBUGS-61766])
+
+* Before this release, command line logs from `virt-launcher` pods were not collected across the Kubernetes cluster, making troubleshooting virtual machines difficult. With this release, command line logs from `virt-launcher` pods are collected and saved in JSON format at `namespaces/{namespace-name}/pods/{pod-name}/virt-launcher.json`, so debugging is possible. (link:https://issues.redhat.com/browse/OCPBUGS-61775[OCPBUGS-61775])
+
+* Before this release, a `systemd` service dependency issue in `nmstate-2.2.48` prevented the service from starting on certain nodes. With this release, the fixed `systemd` unit from upstream is deployed, and allows the service to start correctly while new `nmstate` packages containing the fix are pending. (link:https://issues.redhat.com/browse/OCPBUGS-61859[OCPBUGS-61859])
+
+[id="ocp-4-17-41-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].

modules/zstream-4-17-42.adoc

@@ -0,0 +1,35 @@
+// Module included in the following assemblies:
+//
+// * release_notes/ocp-4-17-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ocp-4-17-42_{context}"]
+= RHBA-2025:18235 - {product-title} {product-version}.42 fixed issues and security update
+
+Issued: 22 October 2025
+
+[role="_abstract"]
+{product-title} release {product-version}.42 is now available. The list of fixed issues that are included in the update is documented in the link:https://access.redhat.com/errata/RHBA-2025:18235[RHBA-2025:18235] advisory. There are no RPM packages for this release.
+
+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.42 --pullspecs
+----
+
+[id="ocp-4-17-42-fixed-issues_{context}"]
+== Fixed issues
+
+* Before this update, multiple mirrors in the {hcp} payload caused image lookup failures, and led to {hcp} creation failures when multiple mirror images were handled. With this release, the {hcp} payload supports multiple mirrors, correctly handles unavailable mirrors, and results in a successful cluster creation. (link:https://issues.redhat.com/browse/OCPBUGS-57143[OCPBUGS-57143])
+
+* Before this update, a fixed upstream issue in {product-title} version 4.17 was not reproducible and was triggered by consuming the issue for downstream. This led to data inconsistency for users. With this release, the upstream issue in the `external-resizer` mechanism is fixed, and reduces potential consumption for downstream. As a result, users do not experience the issue in {product-title} version 4.17. (link:https://issues.redhat.com/browse/OCPBUGS-62466[OCPBUGS-62466])
+
+* Before this update, the incorrect `hostPath` configuration for the `/etc/docker` directory caused {olmv1-first} pod issues. As a consequence, {olmv1} pods failed to work due to a `hostPath` type check error. With this release, the fix ensures the correct directory for `/etc/docker` in `hostPath`, and resolves {olmv1} pod issues. As a result, the {product-title} cluster operates smoothly. (link:https://issues.redhat.com/browse/OCPBUGS-62741[OCPBUGS-62741])
+
+[id="ocp-4-17-42-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].

modules/zstream-4-17-43.adoc

@@ -0,0 +1,45 @@
+// Module included in the following assemblies:
+//
+// * release_notes/ocp-4-17-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ocp-4-17-43_{context}"]
+= RHBA-2025:19314 - {product-title} {product-version}.43 fixed issues and security update
+
+Issued: 5 November 2025
+
+[role="_abstract"]
+{product-title} release {product-version}.43 is now available. The list of fixed issues that are included in the update is documented in the link:https://access.redhat.com/errata/RHBA-2025:19314[RHBA-2025:19314] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:19312[RHBA-2025:19312] 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.43 --pullspecs
+----
+
+[id="ocp-4-17-43-fixed-issues_{context}"]
+== Fixed issues
+
+* Before this update, the stale IP addresses in the `address_set` corresponding to the Domain Name System (DNS) Egress Firewall rule were not removed. This resulted in an ever-growing `address_set` leading to memory leak issues. With this release, the stale IP address are removed from the `address_set` after a 5 second grace period. (link:https://issues.redhat.com/browse/OCPBUGS-61749[OCPBUGS-61749])
+
+* Before this update, the dashboard query template was not updated with the newly selected namespace. As a consequence, there was a difference between the namespace parameter and the query, which caused a rejection of the request. With this release, the dashboard namespace variable is synced with the console's selected namespace in the console. As a result, the synced dashboard variable is filled in the query template, and the backend returns the correct results. (link:https://issues.redhat.com/browse/OCPBUGS-62282[OCPBUGS-62282])
+
+* Before this update, the linked URL was in the developer perspective, but the perspective was not switched when you clicked the link. As a consequence, a blank page was shown. With this release, the perspective changes when you click the link and the page is correctly shown. (link:https://issues.redhat.com/browse/OCPBUGS-63212[OCPBUGS-63212])
+
+* Before this update, the Machine Config Operator (MCO) failed due to multiple labels in the `capacity.cluster-autoscaler.kubernetes.io/labels` annotation in one or more machine sets. With this release, the MCO accepts multiple labels in the `capacity.cluster-autoscaler.kubernetes.io/labels` annotation. As result, the MCO does not fail during the update to 4.19.6. (link:https://issues.redhat.com/browse/OCPBUGS-63364[OCPBUGS-63364])
+
+* Before this update, deleting an `istag` resource with the `--dry-run=server` option unintentionally caused actual deletion of the image from the server. This unexpected deletion occurred due to the `dry-run` option being implemented incorrectly in the `oc delete istag` command. With this release, the `dry-run` option is now wired to the `oc delete istag` command, preventing accidental deletion of image objects. The `istag` object remains intact when using the `--dry-run=server` option. (link:https://issues.redhat.com/browse/OCPBUGS-63392[OCPBUGS-63392])
+
+* Before this update, the **Roles** list page could display invalid data if a regular user had yet to create a project. With this release, the **Roles** list page correctly displays. (link:https://issues.redhat.com/browse/OCPBUGS-63397[OCPBUGS-63397])
+
+* Before this update, it was possible for webhook failures to trigger a `kube-apiserver` crash while generating an audit log entry for a request. As a consequence, API server disruptions were possible. With this release, the audit system has been updated so that the `kube-apiserver` no longer crashes and the API disruptions are resolved. (link:https://issues.redhat.com/browse/OCPBUGS-63460[OCPBUGS-63460])
+
+* Before this update, control plane nodes created before {product-title} 4.12 would not have had the `node-role.kubernetes.io/control-plane` label. With this release, the Machine Config Operator (MCO) adds the label whenever it uncordons a control plane node, if the label was missing. (link:https://issues.redhat.com/browse/OCPBUGS-63540[OCPBUGS-63540])
+
+[id="ocp-4-17-43-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].

modules/zstream-4-17-44-fixed-issues.adoc → modules/zstream-4-17-44.adoc

@@ -3,12 +3,25 @@
 // * release_notes/ocp-4-17-release-notes.adoc
 
 :_mod-docs-content-type: REFERENCE
-[id="zstream-4-17-44-fixed-issues_{context}"]
-= Fixed issues
+[id="zstream-4-17-44-about_{context}"]
+= RHBA-2025:21225 - {product-title} {product-version}.44 fixed issues
+
+Issued: 19 November 2025
 
 [role="_abstract"]
+{product-title} release {product-version}.44 is now available. The list of fixed issues that are included in the update is documented in the link:https://access.redhat.com/errata/RHBA-2025:21225[RHBA-2025:21225] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:21221[RHBA-2025:21221] 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:
 
-The following bugs are fixed for this release:
+[source,terminal]
+----
+$ oc adm release info 4.17.44--pullspecs
+----
+
+[id="zstream-4-17-44-fixed-issues_{context}"]
+== Fixed issues
 
 * Before this update, API and Ingress Virtual IP (VIP) addresses were automatically assigned even when a user-managed load balancer was in use. With this release, the API and Ingress VIPs are no longer automatically assigned. If these values are not explicitly set in the `install-config.yaml`, the installation fails with an error, prompting you to provide them. (link:https://issues.redhat.com/browse/OCPBUGS-53236[OCPBUGS-53236])
 
@@ -22,3 +35,7 @@ The following bugs are fixed for this release:
 
 * Before this update, the Azure machine provider was not passing the `dataDisks` configuration from the `MachineSet` into the virtual machine creation API request for the Azure Stack Hub. As a consequence, new machines were created without the specified data disks because the configuration was silently ignored during the VM creation process. With this release, the VM creation for the Azure Stack Hub is updated to include the `dataDisks` configuration. An additional update manually implements the behavior of the `deletionPolicy: Delete` parameter in the controller because the Azure Stack Hub does not natively support this option. As a result, data disks are correctly provisioned on the Azure Stack Hub VMs. The `Delete` policy is also functionally supported, which ensures that disks are properly removed when their machines are removed. (link:https://issues.redhat.com/browse/OCPBUGS-63700[OCPBUGS-63700])
 
+[id="zstream-4-17-44-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].

modules/zstream-4-17-45-fixed-issues.adoc → modules/zstream-4-17-45.adoc

@@ -3,11 +3,25 @@
 // * release_notes/ocp-4-17-release-notes.adoc
 
 :_mod-docs-content-type: REFERENCE
-[id="zstream-4-17-45-fixed-issues_{context}"]
-= Fixed issues
+[id="zstream-4-17-45-about_{context}"]
+= RHBA-2025:22266 - {product-title} {product-version}.45 fixed issues
+
+Issued: 3 December 2025
 
 [role="_abstract"]
-The following bugs are fixed for this release:
+{product-title} release {product-version}.45 is now available. The list of fixed issues that are included in the update is documented in the link:https://access.redhat.com/errata/RHBA-2025:22266[RHBA-2025:22266] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:22264[RHBA-2025:22264] 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.45--pullspecs
+----
+
+[id="zstream-4-17-45-fixed-issues_{context}"]
+== Fixed issues
 
 * Before this update, URLs passed to the `AlertmanagerConfig` receiver, specifically for Slack and Discord configurations, were not validated. With this release, URL validation is implemented, ensuring that only valid URLs are accepted and invalid ones are rejected. (link:https://issues.redhat.com/browse/OCPBUGS-58408[OCPBUGS-58408])
 
@@ -44,3 +58,8 @@ As a result, the entries are correctly separated. (link:https://issues.redhat.co
 * Before this update, the `ccoctl` utility did not support pagination when retrieving `CloudFront` distributions. As a result, if the distribution to be deleted was not included in the first batch of results, the `CloudFront` distribution and its associated origin access identity could not be deleted successfully during the `ccoctl` {aws-first} delete operation. With this release, pagination support is added to the `ccoctl` utility when fetching `CloudFront` distributions, ensuring that the distribution can be located and deleted properly. (link:https://issues.redhat.com/browse/OCPBUGS-65480[OCPBUGS-65480])
 
 * Before this update, a regression in `runc` prevented pods which had the `shareProcessNamespace` object set to `true` from running properly. With this release, the regression has been corrected. As a result, the underlying issue is resolved, and pods using the `shareProcessNamespace` object can now start and function as expected. (link:https://issues.redhat.com/browse/OCPBUGS-65977[OCPBUGS-65977])
+
+[id="zstream-4-17-45-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].