Open ELENAGER opened 3 months ago
I do not think this is a timeout issue, as the logs indicate the VRG reconcile finds no change that needs further reconciliation and stops further reconciles. At which point only an external change or event would reconcile the resource again, which we are not triggering in the tests as it stands. As a result increasing the timeout will not help in this case.
During the test case we are updating the configMap with an new value (ramenConfig.VolumeUnprotectionEnabled = false). VRG reconcile is reading the updated config map, but we still need time after updating the PVC till the VRG resource will be updated too. I see, that usually we are giving a longer timeout for Eventually function, but in this test it is default - 1 sec. I increased the timeout to 10 seconds and hope it might help.
Fixes: https://github.com/RamenDR/ramen/issues/1372