Bug 2106298 - unix domain socket mode is broken when specified as ovn database transport method
Summary: unix domain socket mode is broken when specified as ovn database transport me...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.12
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.12.0
Assignee: zenghui.shi
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-12 10:15 UTC by zenghui.shi
Modified: 2023-01-17 19:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-17 19:52:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 1188 0 None open Bug 2106298: populate sock address for ovndb connection in unix mode 2022-07-12 10:18:11 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:52:47 UTC

Description zenghui.shi 2022-07-12 10:15:20 UTC 
Description of problem:
ovn-kubernetes supports three transport modes when connecting to ovn databases: ssl, tcp and unix. ssl mode is used in normal openshift deployment, unix sock mode is found to be broken when used in microshift single node deployment.


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


How reproducible:
100%

Steps to Reproduce:
1. set --nb-address and --sb-address to empty string when starting ovnkube-master and ovnkube-node containers will trigger ovnkube to connect with unix socket mode for northbound and southbound databases separately.


Actual results:


Expected results:


Additional info:
Comment 2 zhaozhanqi 2022-08-15 07:23:31 UTC 
Verified this on microshift cluster


$ oc get node -o wide
NAME                    STATUS   ROLES    AGE     VERSION   INTERNAL-IP       EXTERNAL-IP   OS-IMAGE                               KERNEL-VERSION                 CONTAINER-RUNTIME
localhost.localdomain   Ready    <none>   4d13h   v1.23.1   192.168.122.136   <none>        Red Hat Enterprise Linux 8.6 (Ootpa)   4.18.0-372.19.1.el8_6.x86_64   cri-o://1.23.3-11.rhaos4.10.gitddf4b1a.1.el8

[redhat@localhost ~]$ oc get pod -n openshift-ovn-kubernetes
NAME                   READY   STATUS    RESTARTS   AGE
ovnkube-master-kx28h   4/4     Running   0          4d13h
ovnkube-node-hm5pc     1/1     Running   0          4d13h



$ oc get pod -n openshift-ovn-kubernetes ovnkube-node-hm5pc -o yaml | grep -A 10 "ovn-controller"
      echo "$(date -Iseconds) - starting ovn-controller"
      exec ovn-controller unix:/var/run/openvswitch/db.sock -vfile:off \
        --no-chdir --pidfile=/var/run/ovn/ovn-controller.pid \
        --syslog-method="null" \
        --log-file=/var/log/ovn/acl-audit-log.log \
        -vFACILITY:"local0" \
        -vconsole:"${OVN_LOG_LEVEL}" -vconsole:"acl_log:off" \
        -vPATTERN:console:"%D{%Y-%m-%dT%H:%M:%S.###Z}|%05N|%c%T|%p|%m" \
        -vsyslog:"acl_log:info" \
        -vfile:"acl_log:info"
Comment 5 errata-xmlrpc 2023-01-17 19:52:29 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 (Moderate: OpenShift Container Platform 4.12.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:7399
Note You need to log in before you can comment on or make changes to this bug.