Description of problem:

During the upgrade from v111-21 to v111-29, there is more than a minute where our sanity tests fail with timeouts. We have used the Prometheus query rhods_aggregate_availability. The alerts do not fire, so is this the expected behaviour?

We got the same results from v111-29 to v111-34

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. Install RHODS v111-21
2. Launch sanity test job
3. Upgrade RHODS by changing the catalogsource image to v111-29
4. Wait until tests begins in the job
5. oc apply -f catalogsource

Actual results:

Our sanity test seems to have a downtime

https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-sanity/228/robot/report/files/test_report.html#totals

Expected results:

Sanity test pass

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

Additional info: