Description of problem:

If you install RHODS in an OSD cluster and then hibernate the cluster, when resuming it the alert  "RHODS Dashboard Probe Success Burn Rate" fires for a few minutes. I'm not sure if this is a supported scenario, but I wanted to have this documented in a bug just in case.

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

Steps to Reproduce

1. Create an OSD cluster and install RHODS
2. Verify there are no RHODS alerts firing
3. Hibernate the cluster using OCM web console
4. Wait for a few minutes/hours/days
5. Resume the cluster
6. Verify that alert "RHODS Dashboard Probe Success Burn Rate" is firing. It is possible that alert "RHODS Jupyter Probe Success Burn Rate"" also is firing (or in pending stage) for a while

Actual results:

"RHODS Jupyter Probe Success Burn Rate" is firing

Expected results:

As I said, I'm not sure if this is a supported scenario, but it would be better if the alert didn't fire.

Reproducibility (Always/Intermittent/Only Once):

It seems to happen always

Build Details:

I've reproduced this in 2 clusters, one with RHODS 1.19.1 and another with RHODS 1.20.1

Workaround:

Additional info: