Skip to content

Commit fab0314

Browse files
authored
Merge pull request #96944 from tmalove/OSDOCS-59806-4.19
OSDOCS#59806: Correct the bug text for OCPBUGS-43004 for 4.19
2 parents 40e5df3 + 94ff72f commit fab0314

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1894,7 +1894,7 @@ With this release, availability sets are no longer modified after creation, allo
18941894

18951895
* 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])
18961896

1897-
* 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])
1897+
* Previously, a pod with a secondary interface in an OVN-Kubernetes `Localnet` network that was plugged into a `br-ex` interface bridge was out of reach by other pods on the same node, but used the default network for communication. The communication between pods on different nodes was not impacted. With this release, the communication between a `Localnet` pod and a default network pod running on the same node is possible, however the IP addresses that are used in the `Localnet` network must be within the same subnet as the host network. (link:https://issues.redhat.com/browse/OCPBUGS-43004[OCPBUGS-43004])
18981898

18991899
* 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])
19001900

0 commit comments

Comments
 (0)