If a cluster is running with user-workload-monitoring enabled, running an ose-tests suite against the cluster will fail the data collection step.

This is because there is a query in the test framework that assumes that the number of prometheus instances that the thanos pods will connect to will match exactly the number of platform prometheus instances. However, it doesn't account for thanos also connecting to the user-workload-monitoring instances. As such, the test suite will always fail against a cluster that is healthy and running user-workload-monitoring in addition to the normal openshift-monitoring stack.

    

4.15.13
    

Consistent
    

    1. Create an OpenShift cluster
    2. Enable workload monitoring
    3. Attempt to run an ose-tests suite. For example, the CNI conformance suite documented here: https://access.redhat.com/documentation/en-us/red_hat_software_certification/2024/html/red_hat_software_certification_workflow_guide/con_cni-certification_openshift-sw-cert-workflow-working-with-cloud-native-network-function#running-the-cni-tests_openshift-sw-cert-workflow-working-with-container-network-interface
    

The error message `#### at least one Prometheus sidecar isn't ready` will be displayed, and the metrics collection will fail
    

Metrics collection succeeds with no errors