Looking at the charm log I see:
2021-01-12 11:16:54 WARNING ovsdb-relation-changed 2021-01-12T11:16:54Z|00002|jsonrpc|WARN|unix:/var/run/openvswitch/db.sock: receive error: Connection reset by peer
2021-01-12 11:16:54 WARNING ovsdb-relation-changed 2021-01-12T11:16:54Z|00003|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection dropped (Connection reset by peer)
And looking at the Open vSwitch switch log:
2021-01-12T11:16:58.809Z|00002|daemon_unix|ERR|fork child died before signaling startup (killed (Aborted), core dumped)
2021-01-12T11:16:58.809Z|00003|daemon_unix|EMER|could not detach from foreground session
I also see that this is a case of the charm running in a container, this is a dup of bug 1906280
Looking at the charm log I see: changed 2021-01- 12T11:16: 54Z|00002| jsonrpc| WARN|unix: /var/run/ openvswitch/ db.sock: receive error: Connection reset by peer changed 2021-01- 12T11:16: 54Z|00003| reconnect| WARN|unix: /var/run/ openvswitch/ db.sock: connection dropped (Connection reset by peer)
2021-01-12 11:16:54 WARNING ovsdb-relation-
2021-01-12 11:16:54 WARNING ovsdb-relation-
And looking at the Open vSwitch switch log: 12T11:16: 58.809Z| 00002|daemon_ unix|ERR| fork child died before signaling startup (killed (Aborted), core dumped) 12T11:16: 58.809Z| 00003|daemon_ unix|EMER| could not detach from foreground session
2021-01-
2021-01-
I also see that this is a case of the charm running in a container, this is a dup of bug 1906280