Bug 1775838
| Summary: | OVS-CNI does not work with OVN | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jenifer Abrams <jhopper> | |
| Component: | Networking | Assignee: | Alexander Constantinescu <aconstan> | |
| Networking sub component: | ovn-kubernetes | QA Contact: | Meni Yakove <myakove> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | medium | CC: | aconstan, asimha, augol, cnv-qe-bugs, cpaquin, danken, fdeutsch, gkapoor, jcromer, ncredi, phoracek, william.caban, xtian, zzhao | |
| Version: | 4.3.0 | Keywords: | Reopened | |
| Target Milestone: | --- | |||
| Target Release: | 4.3.z | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1806591 (view as bug list) | Environment: | ||
| Last Closed: | 2020-04-30 01:28:07 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1806591 | |||
| Bug Blocks: | 1771572 | |||
|
Description
Jenifer Abrams
2019-11-22 22:32:25 UTC
Also in case it is interesting, here is the ovs-vsctl output from an OVN node: http://perf1.perf.lab.eng.bos.redhat.com/pub/jhopper/OCP4/debug/OVN/ovs-vsctl_OVN.txt Jenifer, thanks for testing OVN with CNV. We aim to tackle its support in future releases. Resolution for this issue is being tracked on Jira. we are tracking it in Jira. closing I'm reopening this issue. We need to run CNV on OCP 4.3 and this bug blocks us from successful deployment. CNV's OVS bridge marker fails on OCP 4.3 with: F0214 13:19:12.260672 1 main.go:42] failed to create a new marker object: Error creating the ovsdb connection: failed to connect to ovsdb error: Invalid socket file The solution would be to backport https://github.com/openshift/cluster-network-operator/pull/357. In this PR, we split OVS and OVN pods, making them share the OVS socket on the host. With the socket available on the host, CNV's OVS bridge marker should be able to successfully start and render the deployment done. Test Environment:
================
$ oc version
Client Version: 4.4.0-0.nightly-2020-04-20-224655
Server Version: 4.4.0-rc.8
Kubernetes Version: v1.17.1
$ oc get csv -n openshift-cnv | awk ' { print $4 } ' | tail -n1
2.3.0
Test Steps:
==========
1. Check status of all the pods under namespace openshift-cnv with app=ovs-cni.
$ oc get pod -n openshift-cnv | grep ovs-cni
ovs-cni-amd64-4jmxb 2/2 Running 3 67m
ovs-cni-amd64-5lzpz 2/2 Running 0 67m
ovs-cni-amd64-7k2xk 2/2 Running 0 67m
ovs-cni-amd64-c679d 2/2 Running 0 67m
ovs-cni-amd64-dxgck 2/2 Running 3 67m
ovs-cni-amd64-w28td 2/2 Running 3 67m
2. Check the logs and see if there are any socket exceptions as mentioned above .
$ for pod in $(oc get pod -n openshift-cnv -l app=ovs-cni --no-headers | awk '{print $1}'); do echo ===$pod=== && oc logs -n openshift-cnv $pod --all-containers=true; done
===ovs-cni-amd64-4jmxb===
I0421 08:49:16.974668 1 main.go:44] Found the OVS socket
===ovs-cni-amd64-5lzpz===
I0421 08:30:59.423366 1 main.go:44] Found the OVS socket
===ovs-cni-amd64-7k2xk===
I0421 08:30:56.322587 1 main.go:44] Found the OVS socket
===ovs-cni-amd64-c679d===
I0421 08:30:55.216315 1 main.go:44] Found the OVS socket
===ovs-cni-amd64-dxgck===
I0421 08:56:24.900515 1 main.go:44] Found the OVS socket
===ovs-cni-amd64-w28td===
I0421 08:42:15.621076 1 main.go:44] Found the OVS socket
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, 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/RHBA-2020:1529 |