'trying to connect' log spam if DB is down

[igsilya]

When database is not available, ovnkube-master logs the trying to connect message every 100 microseconds. This generates a huge amount of logs. Below is the example from the CI upgrade job at the moment databases are upgraded:

I0202 20:29:36.230790      48 client.go:325]  "msg"="trying to connect" "database"="OVN_Southbound" "endpoint"="tcp:172.18.0.2:6642"
I0202 20:29:36.230899      48 client.go:325]  "msg"="trying to connect" "database"="OVN_Southbound" "endpoint"="tcp:172.18.0.2:6642"
I0202 20:29:36.231012      48 client.go:325]  "msg"="trying to connect" "database"="OVN_Southbound" "endpoint"="tcp:172.18.0.2:6642"
I0202 20:29:36.231129      48 client.go:325]  "msg"="trying to connect" "database"="OVN_Southbound" "endpoint"="tcp:172.18.0.2:6642"
I0202 20:29:36.231243      48 client.go:325]  "msg"="trying to connect" "database"="OVN_Southbound" "endpoint"="tcp:172.18.0.2:6642"
I0202 20:29:36.231362      48 client.go:325]  "msg"="trying to connect" "database"="OVN_Southbound" "endpoint"="tcp:172.18.0.2:6642"

These logs can be found in the zipped archive of rotated logs.