Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2152151

Summary: ovn-trace doesn't support connecting to non-leader sbdb
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Patryk Diak <pdiak>
Component: ovn22.06Assignee: Dumitru Ceara <dceara>
Status: CLOSED ERRATA QA Contact: Ehsan Elahi <eelahi>
Severity: low Docs Contact:
Priority: low    
Version: FDP 22.LCC: ctrautma, dceara, jiji, jishi, mmichels, rbrattai
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovn22.06-22.06.0-93.el8fdp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-09 00:27:19 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:

Description Patryk Diak 2022-12-09 13:58:33 UTC 
In HyperShift hosted cluster deployment we often expose the SBDB connection as an openshift route and we only provide one endpoint to ovn-trace, even if SBDB runs in clustered mode.
This is fine for ovn-controller and we can use `--no-leader-only` with ovn-sbctl, ovn-trace doesn't have that option.

debug logs:
#ovn-trace <ssl> --db ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443 ... -v
...
2022-12-09T09:43:12Z|00064|ovsdb_cs|INFO|ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443: clustered database server is not cluster leader; trying another server
2022-12-09T09:43:12Z|00065|reconnect|DBG|ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443: entering RECONNECT
2022-12-09T09:43:12Z|00066|ovsdb_cs|DBG|ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443: SERVER_MONITOR_REQUESTED -> RETRY at lib/ovsdb-cs.c:2011
2022-12-09T09:43:12Z|00067|poll_loop|DBG|wakeup due to 0-ms timeout at lib/reconnect.c:677
2022-12-09T09:43:12Z|00068|reconnect|INFO|ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443: connection attempt timed out
2022-12-09T09:43:12Z|00069|reconnect|DBG|ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443: entering BACKOFF
2022-12-09T09:43:12Z|00070|stream_ssl|DBG|client0-->ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443 type 256 (5 bytes)
2022-12-09T09:43:12Z|00071|stream_ssl|DBG|client0-->ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443 type 257 (1 bytes)
2022-12-09T09:43:12Z|00072|stream_ssl|DBG|client0-->ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443 alert: warning, close_notify (2 bytes)
2022-12-09T09:43:12Z|00073|ovsdb_cs|DBG|ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443: RETRY -> SERVER_SCHEMA_REQUESTED at lib/ovsdb-cs.c:419
ovn-trace: ssl:ovnkube-sbdb-clusters-hypershift-ci-22332.apps.rbratta-o413a42h.qe.devcluster.openshift.com:443: database connection failed ()





How reproducible:
Always




Expected results:
ovn-trace to have an option to work with non-leader sbdb
Comment 1 Dumitru Ceara 2022-12-09 14:14:29 UTC 
V1 posted for review: https://patchwork.ozlabs.org/project/ovn/list/?series=331978&state=*
Comment 2 OVN Bot 2022-12-21 05:05:50 UTC 
ovn22.06 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2155387
ovn22.03 fast-datapath-rhel-8 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2155390
ovn22.03 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2155391
Comment 5 Ehsan Elahi 2023-01-24 11:45:07 UTC 
It seems hard to reproduce as we need to setup an ovn-sandbox to do this. For that purpose, we need to build ovn sources for a sandbox:
make sandbox SANDBOXFLAGS="--sbdb-mode=clustered 
this would spawn ovn in a sandbox and SB will start in clustered mode. 
However from the other tests related to ovn-trace, this seems OK. 
Verifying as sanity Only.
Comment 7 errata-xmlrpc 2023-02-09 00:27:19 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 (ovn22.06 bug fix and enhancement 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/RHBA-2023:0680