OSDOCS-14754:Update the z-stream RNs for 4.16.41

Author: Ted Avery

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

@@ -3362,6 +3362,37 @@ 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.41
+[id="ocp-4-16-41_{context}"]
+=== RHBA-2025:8116 - {product-title} {product-version}.41 bug fix and security update
+
+Issued: 28 May 2025
+
+{product-title} release {product-version}.40 is now available. The list of bug fixes that are included in the update is documented in the link:https://access.redhat.com/errata/RHBA-2025:8116[RHBA-2025:8116] advisory. 
+
+You can view the container images in this release by running the following command:
+
+[source,terminal]
+----
+$ oc adm release info 4.16.41 --pullspecs
+----
+
+[id="ocp-4-16-41-bug-fixes_{context}"]
+==== Bug fixes
+
+* Previously, when you viewed the list of installed Operators, an Operator appeared twice in the list because the currently selected project matched an Operator's default namespace while the copied cluster service versions (CSVs) were disabled in the Operator Lifecycle Manager (OLM). With this release, the Operator appears once. (link:https://issues.redhat.com/browse/OCPBUGS-55644[OCPBUGS-55644]).
+
+* Previously, the Assisted Installer failed to detect World Wide Name (WWN) details during Fibre Channel multipath volumes hardware discovery. As a result, a Fibre Channel multipath disk could not be matched with a WWN root device. This meant that when you specified a `wwn` root device hint, the hint excluded all Fibre Channel multipath disks. With this release, the Assisted Installer now detects WWN details during Fibre Channel multipath disk discovery. If multiple Fibre Channel multipath disks exist, you can now use the `wwn` root device hint to choose a primary disk for your cluster. (link:https://issues.redhat.com/browse/OCPBUGS-55443[OCPBUGS-55443])
+
+* Previously, the `mtu-migration` service did not work correctly when you used `nmstate` to manage a `br-ex` bridge because of a missing service dependency. With this release, the service dependency is now added so that a network configuration that uses `nmstate` to manage a `br-ex` is correct before the migration process begins. (link:https://issues.redhat.com/browse/OCPBUGS-54831[OCPBUGS-54831])
+
+* Previously, when the MAC binding flows on Azure expired, ovs executed a controller action to reinstall that flow. If the ovn-controller was slow right after the flows were deleted, the new flows were not installed in time which reduced the dataplane traffic. With this release, dataplane traffic is not reduced because the new flows are correctly installed by the controller action. (link:https://issues.redhat.com/browse/OCPBUGS-53151[OCPBUGS-53151])
+
+[id="ocp-4-16-41-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 using the CLI].
+
 //4.16.40
 [id="ocp-4-16-40_{context}"]
 === RHSA-2025:4008 - {product-title} {product-version}.40 bug fix and security update