Component Readiness has found a potential regression in [sig-instrumentation] Prometheus [apigroup:image.openshift.io] when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early][apigroup:config.openshift.io] [Skipped:Disconnected] [Suite:openshift/conformance/parallel].

Probability of significant regression: 99.79%

Sample (being evaluated) Release: 4.16
Start Time: 2024-05-08T00:00:00Z
End Time: 2024-05-14T23:59:59Z
Success Rate: 83.33%
Successes: 25
Failures: 5
Flakes: 0

Base (historical) Release: 4.15
Start Time: 2024-02-01T00:00:00Z
End Time: 2024-02-28T23:59:59Z
Success Rate: 100.00%
Successes: 67
Failures: 0
Flakes: 1

View the test details report at https://sippy.dptools.openshift.org/sippy-ng/component_readiness/test_details?arch=amd64&arch=amd64&baseEndTime=2024-02-28%2023%3A59%3A59&baseRelease=4.15&baseStartTime=2024-02-01%2000%3A00%3A00&capability=Other&component=Monitoring&confidence=95&environment=ovn%20no-upgrade%20amd64%20vsphere%20standard&excludeArches=arm64%2Cheterogeneous%2Cppc64le%2Cs390x&excludeClouds=openstack%2Cibmcloud%2Clibvirt%2Covirt%2Cunknown&excludeVariants=hypershift%2Cosd%2Cmicroshift%2Ctechpreview%2Csingle-node%2Cassisted%2Ccompact&groupBy=cloud%2Carch%2Cnetwork&ignoreDisruption=true&ignoreMissing=false&minFail=3&network=ovn&network=ovn&pity=5&platform=vsphere&platform=vsphere&sampleEndTime=2024-05-14%2023%3A59%3A59&sampleRelease=4.16&sampleStartTime=2024-05-08%2000%3A00%3A00&testId=openshift-tests%3Ac1f54790201ec8f4241eca902f854b79&testName=%5Bsig-instrumentation%5D%20Prometheus%20%5Bapigroup%3Aimage.openshift.io%5D%20when%20installed%20on%20the%20cluster%20shouldn%27t%20report%20any%20alerts%20in%20firing%20state%20apart%20from%20Watchdog%20and%20AlertmanagerReceiversNotConfigured%20%5BEarly%5D%5Bapigroup%3Aconfig.openshift.io%5D%20%5BSkipped%3ADisconnected%5D%20%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5D&upgrade=no-upgrade&upgrade=no-upgrade&variant=standard&variant=standard

Notes:

We need to fix the following error:

I0514 12:31:46.014919       1 vsphere_check.go:272] CheckAccountPermissions failed: specified folder not found: folder '/IBMCdatacenter/vm/ci-op-1qvr0jdj-10b01' not found 

This seems to be caused by the new powercli script.  It is creating the folder based on infra id instead of cluster name.  We'll change this to match expected and verify error is resolved.