gnelson/ocp-docs-suggestions-1k-pr huggingface dataset:
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: * Previously, when you used static IP addresses in the customized `br-ex` network bridge configuration of a manifest object, a race condition was added and caused a node reboot operation that further impacted deployment of a cluster. With this release, the `nodeip-configuration` service now starts after the `br-ex` network bridge is up, preventing the race condition and node reboot. (link:https://issues.redhat.com/browse/OCPBUGS-46072[OCPBUGS-46072])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: *  Previously, when a node restarted the `openvswitch` daemon, the `nmstate-handler` container could not access the OpenVSwtich (OVS) database and this caused all OVS-related NNCP configurations to fail. With this release, the issue is fixed. The `nmstate-handler` container can access the OVS database even after restarting the OVS process on the node. The `nmstate-handler` no longer requires a manual restart. (link:https://issues.redhat.com/browse/OCPBUGS-44596[OCPBUGS-44596])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: * Previously, a `MultiNetworkPolicy` API was not enforced when the `protocol` parameter was specified, but the `port` parameter was not, in the cluster configuration. This situation caused all network traffic to reach the cluster. With this release, the `MultiNetworkPolicy` API policy only allows connections from and to the ports specified with the `protocol` parameter so that only specific traffic reaches the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-44354[OCPBUGS-44354])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: * Previously, if an application did not use the Path MTU discovery (PMTUD) mechanism while sending UDP packets larger than the network MTU, an issue with the `OVN` package caused the a packet to be dropped while fragmenting the packet. With this release, the `OVN` package has been fixed so that large UDP packets are properly fragmented and sent over the network. (link:https://issues.redhat.com/browse/OCPBUGS-43649[OCPBUGS-43649])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: * Previously, a pod with an IP address in an OVN-Kubernetes `Localnet` network was unreachable by other pods that ran on the same node but used the default network for communication. Communication between pods on different nodes was not impacted by this communication issue.  With this release, communication between a `Localnet` pod and a default network pod that both run on the same node is possible. (link:https://issues.redhat.com/browse/OCPBUGS-43004[OCPBUGS-43004])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: * Previously, when specific network changes were made to a running cluster, a `NetworkManager` connection profile was permanently created by the `ovs-configuration` service and the profile was incorrectly saved to storage. This profile file would persist through a reboot operation and caused the `ovs-configuration` service to fail. With this release, the `ovs-configuration` cleanup process is updated to remove any unnecessary files, preventing such files from causing issues after a reboot operation. (link:https://issues.redhat.com/browse/OCPBUGS-41489[OCPBUGS-41489])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: *  Previously, the `parseIPList` function failed to handle IP address lists that contained both valid and invalid IP addresses or CIDR ranges. This situation caused the function to return an empty string when it encountered an invalid entry and skip processing valid entries. With this release, the `haproxy.router.openshift.io/ip_allowlist` route annotation skips any invalid IP addresses or CIDR ranges so that the `parseIPList` function can process all listed entries. (link:https://issues.redhat.com/browse/OCPBUGS-39403[OCPBUGS-39403])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: * Previously, the HAProxy router lacked out-of-bounds validation for the `router.openshift.io/haproxy.health.check.interval` annotation. If you set a value that exceeded the maximum value that the HAProxy router could handle, the `router-default` pod could not reach the `Ready` state. With this release, the router now validates the value for the annotation and excludes values that are out of bounds. The router now functions as expected. (link:https://issues.redhat.com/browse/OCPBUGS-38078[OCPBUGS-38078])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: * Previously, in certain situations the gateway IP address for a node changed and caused the `OVN` cluster router, which manages the static route to the cluster subnet, to add a new static route with the new gateway IP address, without deleting the original one. As a result, a stale route still pointed to the switch subnet and this caused intermittent drops during egress traffic transfer. With this release, a patch applied to the `OVN` cluster router ensures that if the gateway IP address changes, the `OVN` cluster router updates the existing static route with the new gateway IP address. A stale route no longer points to the OVN cluster router so that egress traffic flow does not drop. (link:https://issues.redhat.com/browse/OCPBUGS-32754[OCPBUGS-32754])
Original: * Before this update, when a pod used the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might have been unexpectedly deleted. As a consequence, when the pod's DHCP lease expired, the DHCP proxy entered a loop when trying to re-create a new lease, leading to the node becoming unresponsive. With this release, the DHCP lease maintenance terminates if the network interface does not exist. As a result, interface deletions are handled gracefully, which ensures node stability.(link:https://issues.redhat.com/browse/OCPBUGS-45272[*OCPBUGS-45272*])
Revised: * Previously, there was no event logged when an error occurred from a failed conversion from ingress to route. With this update, an error for a failed conversion is logged. (link:https://issues.redhat.com/browse/OCPBUGS-29354[OCPBUGS-29354])
Original: * {product-title} clusters that are installed on {aws-short} in the Mexico Central region (`mx-central-1`) cannot be destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-56020[*OCPBUGS-56020*])
Revised: * {product-title} clusters that are installed on {aws-short} in the Mexico Central region, `mx-central-1`, cannot be destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-56020[OCPBUGS-56020])
Original: * {product-title} clusters that are installed on {aws-short} in the Mexico Central region (`mx-central-1`) cannot be destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-56020[*OCPBUGS-56020*])
Revised: * There is a known issue with RHEL 8 worker nodes that use `cgroupv1` Linux Control Groups (cgroup). The following is an example of the error message displayed for impacted nodes: `UDN are not supported on the node ip-10-0-51-120.us-east-2.compute.internal as it uses cgroup v1.` As a workaround, migrate worker nodes from `cgroupv1` to `cgroupv2`. (link:https://issues.redhat.com/browse/OCPBUGS-49933[OCPBUGS-49933])
Original: * {product-title} clusters that are installed on {aws-short} in the Mexico Central region (`mx-central-1`) cannot be destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-56020[*OCPBUGS-56020*])
* When installing a cluster on {azure-short}, if you set any of the`compute.platform.azure.identity.type`, `controlplane.platform.azure.identity.type`, or `platform.azure.defaultMachinePlatform.identity.type` field values to `None`, your cluster is unable to pull images from the Azure Container Registry. You can avoid this issue by either providing a user-assigned identity, or by leaving the identity field blank. In both cases, the installation program generates a user-assigned identity. (link:https://issues.redhat.com/browse/OCPBUGS-56008[*OCPBUGS-56008*])
Revised: * There is a known issue when the grandmaster clock (T-GM) transitions to the `Locked` state too soon. This happens before the Digital Phase-Locked Loop (DPLL) completes its transition to the `Locked-HO-Acquired` state, and after the Global Navigation Satellite Systems (GNSS) time source is restored. (link:https://issues.redhat.com/browse/OCPBUGS-49826[OCPBUGS-49826])
Original: * {product-title} clusters that are installed on {aws-short} in the Mexico Central region (`mx-central-1`) cannot be destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-56020[*OCPBUGS-56020*])
* When installing a cluster on {azure-short}, if you set any of the`compute.platform.azure.identity.type`, `controlplane.platform.azure.identity.type`, or `platform.azure.defaultMachinePlatform.identity.type` field values to `None`, your cluster is unable to pull images from the Azure Container Registry. You can avoid this issue by either providing a user-assigned identity, or by leaving the identity field blank. In both cases, the installation program generates a user-assigned identity. (link:https://issues.redhat.com/browse/OCPBUGS-56008[*OCPBUGS-56008*])
* When installing a cluster on {aws-short}, if you did not configure {aws-short} credentials before running any `openshift-install create` command, the installation program will fail. (link:https://issues.redhat.com/browse/OCPBUGS-56658[*OCPBUGS-56658*])
Revised: * When installing a cluster on {azure-short}, if you set any of the `compute.platform.azure.identity.type`, `controlplane.platform.azure.identity.type`, or `platform.azure.defaultMachinePlatform.identity.type` field values to `None`, your cluster is unable to pull images from the Azure Container Registry. You can avoid this issue by either providing a user-assigned identity, or by leaving the identity field blank. In both cases, the installation program generates a user-assigned identity. (link:https://issues.redhat.com/browse/OCPBUGS-56008[OCPBUGS-56008])
Original: * {product-title} clusters that are installed on {aws-short} in the Mexico Central region (`mx-central-1`) cannot be destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-56020[*OCPBUGS-56020*])
* When installing a cluster on {azure-short}, if you set any of the`compute.platform.azure.identity.type`, `controlplane.platform.azure.identity.type`, or `platform.azure.defaultMachinePlatform.identity.type` field values to `None`, your cluster is unable to pull images from the Azure Container Registry. You can avoid this issue by either providing a user-assigned identity, or by leaving the identity field blank. In both cases, the installation program generates a user-assigned identity. (link:https://issues.redhat.com/browse/OCPBUGS-56008[*OCPBUGS-56008*])
* When installing a cluster on {aws-short}, if you did not configure {aws-short} credentials before running any `openshift-install create` command, the installation program will fail. (link:https://issues.redhat.com/browse/OCPBUGS-56658[*OCPBUGS-56658*])
Revised: * When installing a cluster on {aws-short}, if you did not configure {aws-short} credentials before running any `openshift-install create` command, the installation program fails. (link:https://issues.redhat.com/browse/OCPBUGS-56658[OCPBUGS-56658])
Original: * {product-title} clusters that are installed on {aws-short} in the Mexico Central region (`mx-central-1`) cannot be destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-56020[*OCPBUGS-56020*])
* When installing a cluster on {azure-short}, if you set any of the`compute.platform.azure.identity.type`, `controlplane.platform.azure.identity.type`, or `platform.azure.defaultMachinePlatform.identity.type` field values to `None`, your cluster is unable to pull images from the Azure Container Registry. You can avoid this issue by either providing a user-assigned identity, or by leaving the identity field blank. In both cases, the installation program generates a user-assigned identity. (link:https://issues.redhat.com/browse/OCPBUGS-56008[*OCPBUGS-56008*])
* When installing a cluster on {aws-short}, if you did not configure {aws-short} credentials before running any `openshift-install create` command, the installation program will fail. (link:https://issues.redhat.com/browse/OCPBUGS-56658[*OCPBUGS-56658*])
Revised: The `must-gather` tool does not collect IPsec information for a cluster that was upgraded from {product-title} 4.14. This issue occurs because the `ipsecConfig` configuration in the `networks.operator.openshift.io cluster` CR has an empty construct, `{}`. The empty construct is passed to the upgraded version of {product-title}. As a workaround for this issue, run the following command with the following `ipsecConfig`  configuration in the Cluster Network Operator (CNO) CR:
Original: * {product-title} clusters that are installed on {aws-short} in the Mexico Central region (`mx-central-1`) cannot be destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-56020[*OCPBUGS-56020*])
* When installing a cluster on {azure-short}, if you set any of the`compute.platform.azure.identity.type`, `controlplane.platform.azure.identity.type`, or `platform.azure.defaultMachinePlatform.identity.type` field values to `None`, your cluster is unable to pull images from the Azure Container Registry. You can avoid this issue by either providing a user-assigned identity, or by leaving the identity field blank. In both cases, the installation program generates a user-assigned identity. (link:https://issues.redhat.com/browse/OCPBUGS-56008[*OCPBUGS-56008*])
* When installing a cluster on {aws-short}, if you did not configure {aws-short} credentials before running any `openshift-install create` command, the installation program will fail. (link:https://issues.redhat.com/browse/OCPBUGS-56658[*OCPBUGS-56658*])
Revised: After you run the command, the CNO collects `must-gather` logs that you can inspect.
Original: * Previously, a console plugin could be enabled multiple times in the Console plugin enablement modal, resulting in multiple entries for the plugin appearing the Console Operator Configuration.  With this release, it is no longer possible to enable a plugin if it is already enabled. (link:https://issues.redhat.com/browse/OCPBUGS-44595[OCPBUGS-44595])
Revised: * Previously, a console plugin could be enabled multiple times in the Console plugin enablement modal, resulting in multiple entries for the plugin appearing the Console Operator Configuration. With this release, it is no longer possible to enable a plugin if it is already enabled. (link:https://issues.redhat.com/browse/OCPBUGS-44595[OCPBUGS-44595])
Original: * Previously, the shared Timestamp component referenced an undefined property when calculating relative times. As a result, most times displayed in the console were not correctly displaying relative strings like "Just now" or "Less than a minute ago". With this release, the issue is fixed and relative time strings are correctly rendered in the console. (link:https://issues.redhat.com/browse/OCPBUGS-51202[OCPBUGS-51202])
Revised: * Previously, the shared Timestamp component referenced an undefined property when calculating relative times. As a result, most times displayed in the console were not correctly displaying relative strings such as "Just now" or "Less than a minute ago". With this release, the issue is fixed and relative time strings are correctly rendered in the console. (link:https://issues.redhat.com/browse/OCPBUGS-51202[OCPBUGS-51202])
Original: * Previously, the Selects above the Node Logs did not close when opened, unless the Select's toggle was clicked again or one of the Select's menu items was clicked. With this release, the Select closes after clicking outside of the menu or by pressing the appropriate key on the keyboard. (link:https://issues.redhat.com/browse/OCPBUGS-52316[OCPBUGS-52316])
Revised: * Previously, the Select above the Node Logs did not close when opened, unless the Select's toggle was clicked again or one of the Select's menu items was clicked. With this release, the Select closes after clicking outside of the menu or by pressing the appropriate key on the keyboard. (link:https://issues.redhat.com/browse/OCPBUGS-52316[OCPBUGS-52316])
Original: * Previously, the console alerted users that worker nodes must be updated within 60 days when performing a control plane only update. With this release, the console no longer displays this invalid alert. (link:https://issues.redhat.com/browse/OCPBUGS-56077[OCPBUGS-56077])
Revised: * Previously, the console alerted users that compute nodes must be updated within 60 days when performing a control plane only update. With this release, the console no longer displays this invalid alert. (link:https://issues.redhat.com/browse/OCPBUGS-56077[OCPBUGS-56077])
Original: * Previously, the Critical Alerts section of the Notification Drawer could not be collapsed. With this release, the section can be collapsed. (link:https://issues.redhat.com/browse/OCPBUGS-55702[OCPBUGS-55702])
Revised: * Previously, the *Critical Alerts* section of the *Notification Drawer* could not be collapsed. With this release, the section can be collapsed. (link:https://issues.redhat.com/browse/OCPBUGS-55702[OCPBUGS-55702])
Original: * Previously, the link to OperatorHub in the Installed Operators page would trigger a hard reload. With this release, this link no longer triggers a hard reload. (link:https://issues.redhat.com/browse/OCPBUGS-54536[OCPBUGS-54536])
Revised: * Previously, the link to OperatorHub in the *Installed Operators* page would trigger a hard reload. With this release, this link no longer triggers a hard reload. (link:https://issues.redhat.com/browse/OCPBUGS-54536[OCPBUGS-54536])
Original: * Previously, there was incorrect logic for calculating the pod container count causing it to be inaccurate. With this release,  the `Ready` and `Started` status in count logic was added so the correct pod container count is displayed, which is consist with `oc` CLI. (link:https://issues.redhat.com/browse/OCPBUGS-53118[OCPBUGS-53118])
Revised: * Previously, there was incorrect logic for calculating the pod container count causing it to be inaccurate. With this release, the `Ready` and `Started` status in count logic was added so the correct pod container count is displayed, which is consist with `oc` CLI. (link:https://issues.redhat.com/browse/OCPBUGS-53118[OCPBUGS-53118])
Original: * Previously, when viewing the list of installed Operators, an Operator appeared twice in the list if the currently selected project matched an Operator's default namespace while copied CSVs were disabled in {olm-first}. With this release, the Operator appears only once in such cases. (link:https://issues.redhat.com/browse/OCPBUGS-54601[OCPBUGS-54601])
Revised: * Previously, when viewing the list of installed Operators, an Operator displayed twice in the list if the currently selected project matched an Operator's default namespace while copied CSVs were disabled in {olm-first}. With this release, the Operator only displays once in such cases. (link:https://issues.redhat.com/browse/OCPBUGS-54601[OCPBUGS-54601])