With the revert of OVN version to fix the ovn-controller crash here: We no longer have the fix for conjunction warnings: https://bugzilla.redhat.com/show_bug.cgi?id=1933752 This is to track bumping OVN in 4.6z to get the fixes. This is a noop for 4.7 and 4.8.
(In reply to Tim Rozet from comment #1) > With the revert of OVN version to fix the ovn-controller crash here: > https://bugzilla.redhat.com/show_bug.cgi?id=1945725 > We no longer have the fix for conjunction warnings: > https://bugzilla.redhat.com/show_bug.cgi?id=1933752 > > This is to track bumping OVN in 4.6z to get the fixes. This is a noop for > 4.7 and 4.8.
Anurag, do you mind verifying this? It is essentially a noop as we do not need to bump the OVN version here or in 4.7. You could do some sanity check on the OVN logs on a periodic 4.7/4.8 job to ensure there are no conjunction warnings as a sanity check.
Checked on 4.8.0-0.nightly-2021-04-09-222447 no conjunction warning logs found. for f in $(oc -n openshift-ovn-kubernetes get pod -l app=ovnkube-node -o jsonpath={.items[*].metadata.name}) ; do echo -e "\n${f}\n" ; oc -n openshift-ovn-kubernetes logs "${f}" -c ovn-controller | grep conjunction ; done ovnkube-node-75krh ovnkube-node-d969p ovnkube-node-r9djt ovnkube-node-scnpg ovnkube-node-vr4h8 Move this to 'verified'
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days