Merge pull request openshift#78053 from cbippley/OSDOCS-9882-missed-bugs

OSDOCS-9882 Adding overlooked issues to 4.16 RNs

Author: JoeAldinger

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

@@ -877,7 +877,7 @@ The Telemetry and the Insights Operator collects telemetry on IPsec connections.
 [id="overlapping-ip-configuration-multi-tenant-networks-whereabouts"]
 ==== Overlapping IP configuration for multi-tenant networks with Whereabouts
 
-Previously, it was not possible to configure the same CIDR range twice and to have the Whereabouts CNI plugin assign IP addresses from these ranges independently. This limitation caused issues in multi-tenant environments where different groups might need to select overlapping CIDR ranges. 
+Previously, it was not possible to configure the same CIDR range twice and to have the Whereabouts CNI plugin assign IP addresses from these ranges independently. This limitation caused issues in multi-tenant environments where different groups might need to select overlapping CIDR ranges.
 
 With this release, the Whereabouts CNI plugin supports overlapping IP address ranges through the inclusion of a `network_name` parameter. Administrators can use the `network_name` parameter to configure the same CIDR range multiple times within separate `NetworkAttachmentDefinitions`, which enables independent IP address assignments for each range.
 
@@ -1878,6 +1878,8 @@ Kubernetes 1.29 removed the following deprecated APIs, so you must migrate manif
 
 * Previously, the `inspector.ipxe` configuration file used the `IRONIC_IP` variable, which did not account for IPv6 addresses because they have brackets. Consequently, when the user supplied an incorrect `boot_mac_address`, iPXE fell back to the `inspector.ipxe` configuration file, which supplied a malformed IPv6 host header since it did not contain brackets. With this release, the `inspector.ipxe` configuration file has been updated to use the `IRONIC_URL_HOST` variable, which accounts for IPv6 addresses and resolves the issue. (link:https://issues.redhat.com/browse/OCPBUGS-22699[*OCPBUGS-22699*])
 
+* Previously, Ironic Python Agent assumed all server disks to have a 512 byte sector size when trying to wipe disks. This caused the disk wipe to fail. With this release, Ironic Python Agent checks the disk sector size and has separate values for disk wiping so that the disk wipe succeeds. (link:https://issues.redhat.com/browse/OCPBUGS-31549[*OCPBUGS-31549*])
+
 [discrete]
 [id="ocp-4-16-builds-bug-fixes_{context}"]
 ==== Builds
@@ -2043,6 +2045,8 @@ The issue is resolved in this release. (link:https://issues.redhat.com/browse/OC
 
 * With this update, the size is reduced for audit log files that are stored in the `kube-apiserver`, `openshift-apiserver`, and `oauth-apiserver` pods for hosted control planes. (link:https://issues.redhat.com/browse/OCPBUGS-31106[*OCPBUGS-31106*])
 
+* Previously, the Hypershift Operator was not using the `RegistryOverrides` mechanism to inspect the image from the internal registry. With this release, the metadata inspector works as expected during the Hypershift Operator reconciliation, and the `OverrideImages` are properly populated. (link:https://issues.redhat.com/browse/OCPBUGS-29494[*OCPBUGS-29494*])
+
 [discrete]
 [id="ocp-4-16-image-registry-bug-fixes_{context}"]
 ==== Image Registry
@@ -2185,6 +2189,8 @@ With this update, as the Agent-based installation method does not require libvir
 
 * Previously, Agent-based installations created `ImageContentSource` objects instead of `ImageDigestSources` even though the former object is deprecated. With this release, the Agent-based installation program creates `ImageDigestSource` objects. (link:https://issues.redhat.com/browse/OCPBUGS-11665[*OCPBUGS-11665*])
 
+* Previously, there was an issue with the destroy functionality of the Power VS where not all resources were deleted as expected. With this release, the issue has been resolved. (link:https://issues.redhat.com/browse/OCPBUGS-29425[*OCPBUGS-29425*])
+
 [discrete]
 [id="ocp-4-16-insights-operator-bug-fixes_{context}"]
 ==== Insights Operator
@@ -2365,6 +2371,10 @@ With this update, as the Agent-based installation method does not require libvir
 
 * Previously, when the default gateway of a node was set to `vlan` and multiple network manager connection had the same name, the node would fail as it could not configure the default OVN-Kubernetes bridge. With this release, the `configure-ovs.sh` shell script includes an `nmcli connection show uuid` command that retrieves the correct network manager connection if many connections with the same name exist. (link:https://issues.redhat.com/browse/OCPBUGS-24356[*OCPBUGS-24356*])
 
+* For {product-title} clusters on {azure-full}, when using OVN-Kubernetes as the Container Network Interface (CNI), there was an issue where the source IP recognized by the pod was the OVN gateway router of the node when using a load balancer service with `externalTrafficPolicy: Local`. This occurred due to a Source Network Address Translation (SNAT) being applied to UDP packets.
++
+With this update, session affinity without a timeout is possible by setting the affinity timeout to a higher value, for example, `86400` seconds, or 24 hours. As a result, the affinity is treated as permanent unless there are network disruptions like endpoints or nodes going down. As a result, session affinity is more persistent. (link:https://issues.redhat.com/browse/OCPBUGS-24219[*OCPBUGS-24219*])
+
 [discrete]
 [id="ocp-4-16-node-bug-fixes_{context}"]
 ==== Node
@@ -2423,6 +2433,8 @@ To retain the catalog rebuilding functionality, use `--rebuild-catalog`. However
 
 * Previously, role bindings related to the `ImageRegistry`, `Build`, and `DeploymentConfig` capabilities were created in every namespace, even if the capability was disabled. With this release, the role bindings are only created if the cluster capability is enabled on the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-34384[*OCPBUGS-34384*])
 
+* Previously, during the disk-to-mirror process for fully disconnected environments, oc-mirror plugin v1 would fail to mirror the catalog image when access to Red Hat registries was blocked. Additionally, if the `ImageSetConfiguration` used a `targetCatalog` for the mirrored catalog, mirroring would fail due to incorrect catalog image references regardless of the workflow. This issue has been resolved by updating the catalog image source for mirroring to the mirror registry. (link:https://issues.redhat.com/browse/OCPBUGS-34646[*OCPBUGS-34646*])
+
 [discrete]
 [id="ocp-4-16-olm-bug-fixes_{context}"]
 ==== Operator Lifecycle Manager (OLM)
@@ -3162,6 +3174,7 @@ In the following tables, features are marked with the following statuses:
 * Enabling LUKS encryption on a system using 512 emulation disks causes provisioning to fail and the system launches the emergency shell in the initramfs. This happens because of an alignment bug in `sfdisk` when growing a partition. As a workaround, you can use Ignition to perform the resizing instead. (link:https://issues.redhat.com/browse/OCPBUGS-35410[*OCPBUGS-35410*])
 
 [id="ocp-telco-ran-4-16-known-issues_{context}"]
+
 * The current PTP grandmaster clock (T-GM) implementation has a single National Marine Electronics Association (NMEA) sentence generator sourced from the GNSS without a backup NMEA sentence generator.
 If NMEA sentences are lost before reaching the e810 NIC, the T-GM cannot synchronize the devices in the network synchronization chain and the PTP Operator reports an error.
 A proposed fix is to report a `FREERUN` event when the NMEA string is lost.
@@ -3200,7 +3213,7 @@ metadata:
 data:
   mtu: "1500" <1>
 ----
-<1> The `mtu` value must be aligned with the MTU of the node interface. 
+<1> The `mtu` value must be aligned with the MTU of the node interface.
 +
 (link:https://issues.redhat.com//browse/OCPBUGS-35316[*OCPBUGS-35316*])