Loading...

XML

Word

Printable

Release Note Status:
Done
Release Note Type:
Bug Fix
Release Note Text:

Hide
* Previously, when a node restarted the `openvswitch` daemon, the `nmstate-handler` container could not access the OVS database and this caused all OVS-related NNCP configurations to fail. With this release, the issue is fixed and 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~~])

Show
* Previously, when a node restarted the `openvswitch` daemon, the `nmstate-handler` container could not access the OVS database and this caused all OVS-related NNCP configurations to fail. With this release, the issue is fixed and 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 ])

Description of problem:

When node restarted openvswitch daemon, the nmstate-handler container will
got no access to the OVS DB which cause all OVS related NNCP fails.

Version-Release number of selected component (if applicable):

How reproducible:


100%

Steps to Reproduce:

oc debug node/worker-0
chroot /host
systemctl restart openvswitch
# when apply a NNCP with OVS

Actual results:


NNCP fails with verification error on OVS port missmatch

Expected results:

No failure

Additional info:

links to

RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update