Merge pull request #77948 from dfitzmau/OSDOCS-9882-networking-2

OSDOCS-0992-networking-2: Documented the 2nd round of bug batching fo…

Author: ShaunaDiaz

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

@@ -2046,6 +2046,14 @@ With this release, the CCO no longer checks for the nonexistent permission.
 
 * Previously, the image registry Azure path-fix job incorrectly required the presence of `AZURE_CLIENT_ID` and `TENANT_CLIENT_ID` parameters to function. This caused a valid configuration to throw an error message. With this release, a check is added to the Identity and Access Management (IAM) service account key to validate if these parameters are needed, so that a cluster upgrade operation no longer fails. (link:https://issues.redhat.com/browse/OCPBUGS-32328[*OCPBUGS-32328*])
 
+* Previously, the image registry did not support {aws-first} region `ca-west-1`. With this release, the image registry can now be deployed in this region. (link:https://issues.redhat.com/browse/OCPBUGS-29233[*OCPBUGS-29233*])
+
+* Previously, when the `virtualHostedStyle` parameter was set to `regionEndpoint` in the Image Registry Operator configuration, the image registry ignored the virtual hosted style configuration. With this release, the issue is resolved so that a new upstream distribution configuration, force path style, is used instead of the downstream only version, virtual hosted style. (link:https://issues.redhat.com/browse/OCPBUGS-34166[*OCPBUGS-34166*])
+
+* Previously, when running an {product-title} cluster on {ibm-power-server-name} where service-endpoint override was enabled, the Cloud Credential Operator (CCO) Operator would ignore the overriding service endpoints. With this release, the CCO Operator no longer ignores overriding service endpoints. (link:https://issues.redhat.com/browse/OCPBUGS-32491[*OCPBUGS-32491*])
+
+* Previously, the Image Registry Operator ignored endpoint service cluster-level overrides, making configuring your cluster in an {ibm-cloud-name} disconnected environment difficult. This issue only existed on installer-provisioned infrastructure. With this release, the Image Registry Operator no longer ignores these cluster-level overrides. (link:https://issues.redhat.com/browse/OCPBUGS-26064[*OCPBUGS-26064*])
+
 [discrete]
 [id="ocp-4-16-installer-bug-fixes_{context}"]
 ==== Installer
@@ -2292,6 +2300,10 @@ With this update, as the Agent-based installation method does not require libvir
 
 * Previously, the console redirect service had the same service Certificate Authority (CA) controller annotation as the console service. This caused the service CA controller to sometimes incorrectly sync CA certs for these services, and the console would not function correctly after removing and reinstalling. With this release, the console Operator was updated to remove this service CA annotation from the console redirect service. The console services and CA certs now function as expected when the Operator transitions from a removed to a managed state. (link:https://issues.redhat.com/browse/OCPBUGS-7656[*OCPBUGS-7656*])
 
+* Previously, removing an alternate service when editing a Route by using the *Form view* did not result in the removal of the alternate service from the Route. With this update, the alternate service is now removed. (link:https://issues.redhat.com/browse/OCPBUGS-33011[*OCPBUGS-33011*])
+
+* Previously, nodes of paused `MachineConfigPools` migh be incorrectly unpaused when performing a cluster update. With this release, nodes of paused `MachineConfigPools` correctly stay paused when performing a cluster update. (link: https://issues.redhat.com/browse/OCPBUGS-23319[*OCPBUGS-23319*])
+
 [discrete]
 [id="ocp-4-16-monitoring-bug-fixes_{context}"]
 ==== Monitoring
@@ -2329,22 +2341,17 @@ With this update, as the Agent-based installation method does not require libvir
 * Previously, when a MAC address changed on the physical interface being used by OVN-Kubernetes, it would not be updated correctly within OVN-Kubernetes and could cause traffic disruption and Kube API outages from the node for a prolonged period of time. This was most common when a bond interface was being used, where the MAC address of the bond might swap depending on which device was the first to come up. With this release, the issues if fixed so that OVN-Kubernetes dynamically detects MAC address changes and updates it correctly. (link:https://issues.redhat.com/browse/OCPBUGS-18716[*OCPBUGS-18716*])
 
 * Previously, the global navigation satellite system (GNSS) module was capable of reporting both the GPS `fix` position and the GNSS `offset` position, which represents the offset between the GNSS module and the constellations. The previous T-GM did not use the `ubloxtool` CLI tool to probe the `ublox` module for reading `offset` and `fix` positions. Instead, it could only read the GPS `fix` information via GPSD. The reason for this was that the previous implementation of the `ubloxtool` CLI tool took 2 seconds to receive a response, and with every call it increased CPU usage by threefold. With this release, the `ubloxtool` request is now optimized, and the GPS `offset` position is now available. (link:https://issues.redhat.com/browse/OCPBUGS-17422[*OCPBUGS-17422*])
+
 * Previously, `EgressIP` pods hosted by a secondary interface would not failover because of a race condition. Users would receive an error message indicating that the `EgressIP` pod could not be assigned because it conflicted with an existing IP address. With this release, the `EgressIP` pod moves to an egress node. (https://issues.redhat.com/browse/OCPBUGS-20209[*OCPBUGS-20209*])
 
 * Previously, when a MAC address changed on the physical interface being used by OVN-Kubernetes, it would not be updated correctly within OVN-Kubernetes and could cause traffic disruption and Kube API outages from the node for a prolonged period of time. This was most common when a bond interface was being used, where the MAC address of the bond might swap depending on which device was the first to come up. With this release, the issues if fixed so that OVN-Kubernetes dynamically detects MAC address changes and updates it correctly. (link:https://issues.redhat.com/browse/OCPBUGS-18716[*OCPBUGS-18716*])
 
-* Previously, the global navigation satellite system (GNSS) module was capable of reporting both the GPS `fix` position and the GNSS `offset` position, which represents the offset between the GNSS module and the constellations. The previous T-GM did not use the `ubloxtool` CLI tool to probe the `ublox` module for reading `offset` and `fix` positions. Instead, it could only read the GPS `fix` information via GPSD. The reason for this was that the previous implementation of the `ubloxtool` CLI tool took two seconds to receive a response, and with every call it increased CPU usage by threefold. With this release, the `ubloxtool` request is now optimized, and the GPS `offset` position is now available. (link:https://issues.redhat.com/browse/OCPBUGS-17422[*OCPBUGS-17422*])
-
-////
-* Previously for {product-title} clusters on {azure-full} that used OVN-Kubernetes as the Container Network Interface (CNI), an issue existed where the source IP recognized by the pod was the OVN gateway router of the node when the load balancer service with `externalTrafficPolicy: Local` was used. This occurred due to a Source Network Address Translation (SNAT) being applied to UDP packets.
-+
-With this release, 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 such as endpoints or nodes going down. As a result, session affinity is more persistent. (link:https://issues.redhat.com/browse/OCPBUGS-24219[*OCPBUGS-24219*])
-////
-
 * Previously, IPv6 was unsupported when assigning an egress IP to a network interface that was not the primary network interface. This issue has been resolved, and the egress IP can be IPv6. (https://issues.redhat.com/browse/OCPBUGS-24271[*OCPBUGS-24271*])
 
 * Previously, the `network-tools` image, which is a debugging tool, included the Wireshark network protocol analyzer. Wireshark had a dependency on the `gstreamer1` package, and this package has specific licensing requirements. With this release, the `gstreamer1` package is removed from the network-tools image and the image now includes the `wireshark-cli` package.(link:https://issues.redhat.com/browse/OCPBUGS-31699[*OCPBUGS-31699*])
 
+* 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*])
+
 [discrete]
 [id="ocp-4-16-node-bug-fixes_{context}"]
 ==== Node