Bug 2047710 - [OVN] ovn-dbchecker CrashLoopBackOff and sbdb jsonrpc unix socket receive error
Summary: [OVN] ovn-dbchecker CrashLoopBackOff and sbdb jsonrpc unix socket receive error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.11.0
Assignee: Surya Seetharaman
QA Contact: Ross Brattain
URL:
Whiteboard:
Depends On: 2033514
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-28 11:39 UTC by Surya Seetharaman
Modified: 2022-08-23 19:39 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 2033514
Environment:
Last Closed: 2022-08-23 19:39:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 980 0 None open Bug 2047710: Bump OVS version to 2.16.0-57.el8fdp 2022-04-02 19:22:50 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-23 19:39:57 UTC

Comment 1 Surya Seetharaman 2022-01-28 11:41:08 UTC 
This bz is simply to track the OVS bump needed once https://bugzilla.redhat.com/show_bug.cgi?id=2033514 is fixed.
Comment 5 Ross Brattain 2022-04-12 05:00:33 UTC 
Verified on 4.11.0-0.nightly-2022-04-11-200046  install succeeded on IBM Cloud IPI

Host OVS
Red Hat Enterprise Linux CoreOS 411.85.202203242008-0 (Ootpa)
openvswitch2.16-2.16.0-57.el8fdp.x86_64

ovnkube-node-zxmfb
openvswitch2.16-2.16.0-57.el8fdp.x86_64
Comment 7 errata-xmlrpc 2022-08-23 19:39:39 UTC 
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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069
Note You need to log in before you can comment on or make changes to this bug.