libovsdb: give monitor setup time to process than normal transactions

In certain scaling situations, it may take longer than types.OVSDBTimeout for the
monitoring of OVSDB tables to be set up. This change is a follow-up to commit
da9408d, accounting for cases where ovnkube-master
has a lot of startup data. The timeout for monitoring introduced in commit
6ae4edb did not account for that.

Reported-at: https://issues.redhat.com/browse/OCPBUGS-17147
Signed-off-by: Flavio Fernandes <[email protected]>

go-controller/pkg/libovsdb/libovsdb.go

@@ -98,7 +98,7 @@ func NewSBClientWithConfig(cfg config.OvnAuthConfig, promRegistry prometheus.Reg
 		return nil, err
 	}
 
-	ctx, cancel := context.WithTimeout(context.Background(), types.OVSDBTimeout)
+	ctx, cancel := context.WithTimeout(context.Background(), types.OVSDBTimeout*2)
 	go func() {
 		<-stopCh
 		cancel()
@@ -166,7 +166,7 @@ func NewNBClientWithConfig(cfg config.OvnAuthConfig, promRegistry prometheus.Reg
 		return nil, err
 	}
 
-	ctx, cancel := context.WithTimeout(context.Background(), types.OVSDBTimeout)
+	ctx, cancel := context.WithTimeout(context.Background(), types.OVSDBTimeout*2)
 	go func() {
 		<-stopCh
 		cancel()