I do not think there is much more we can do on this bz without core dumps.
Since case is closed, I'm going to also close this bz. Please re-open or create a new issue if that is needed.

In order to collect core dumps in the OCP, you use the command:

    oc adm must-gather --dest-dir="./netwowk_ovn" -- gather_core_dumps
 
Granted we have that, we can ask the OVN core folks for help to see if they we explain why we had the following
issue in ovn-northd.

Thanks,

-- flavio


```
           PID: 5890 (ovsdb-client)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Tue 2021-06-29 08:04:07 UTC (1 months 26 days ago)
  Command Line: ovsdb-client -t 30 wait unix:/var/run/ovn/ovnnb_db.sock OVN_Northbound connected
    Executable: /usr/bin/ovsdb-client
 Control Group: /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod5906b614_6058_4461_b0ef_c6560828cace.slice/crio-773283acba935f8ffbad97b69e51>
          Unit: crio-773283acba935f8ffbad97b69e516695f5b521d2d0df455a8192c8c9be6829d4.scope
         Slice: kubepods-burstable-pod5906b614_6058_4461_b0ef_c6560828cace.slice
       Boot ID: 75c50b6ae4ae405880c35ade3c3930df
    Machine ID: 648697703669495f87e1b66e56f05876
      Hostname: cirrus-mnsx4-master-0
       Storage: /var/lib/systemd/coredump/core.ovsdb-client.0.75c50b6ae4ae405880c35ade3c3930df.5890.1624953847000000.lz4 (inaccessible)
       Message: Process 5890 (ovsdb-client) of user 0 dumped core.

                Stack trace of thread 83:
                #0  0x0000563c7ec3f400 n/a (/usr/bin/ovsdb-client)

           PID: 4524 (ovn-northd)
```