-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
-
False
-
-
In recent test run you can see how TestCustomPrometheus fails some times:
custom_prometheus_test.go:43: STEP 1: Installing Prometheus operator
custom_prometheus_test.go:44: Creating namespaces: [custom-prometheus]
custom_prometheus_test.go:47:
custom_prometheus_test.go:47: STEP 2: Creating SMCP with Prometheus extension provider
custom_prometheus_test.go:50:
custom_prometheus_test.go:50: STEP 3: Installing custom Prometheus
custom_prometheus_test.go:53:
custom_prometheus_test.go:53: STEP 4: Intalling Bookinfo app
custom_prometheus_test.go:54: Wait for condition condition=Ready on smcp istio-system/basic...
custom_prometheus_test.go:54: SUCCESS: Condition condition=Ready met by smcp istio-system/basic
custom_prometheus_test.go:56: Create Bookinfo Gateway
custom_prometheus_test.go:56: Create Bookinfo Destination Rules (all)
custom_prometheus_test.go:56: Create Bookinfo Deployments
custom_prometheus_test.go:58:
custom_prometheus_test.go:58: STEP 5: Enabling telemetry
custom_prometheus_test.go:61:
custom_prometheus_test.go:61: STEP 6: Enabling monitoring
custom_prometheus_test.go:66:
custom_prometheus_test.go:66: STEP 7: Waiting for installs to complete
custom_prometheus_test.go:114: FATAL: Command failed: oc -n 'custom-prometheus' wait 'subscription/rhods-prometheus-operator' --for 'jsonpath={.status.installPlanRef.kind}=InstallPlan' --timeout 1s
error: installPlanRef is not found
error: exit status 1
test.go:77:
test.go:79: Test failed in 104.81s (excluding cleanup)
test.go:95: Capturing cluster state using must-gather registry.redhat.io/openshift-service-mesh/istio-must-gather-rhel8:2.4
test.go:99: /home/jenkins/workspace/maistra/maistra-test-tool/maistra-test-tool/tests/result-20230628161807/v2.4/failures-must-gather/20230628164729-TestCustomPrometheus
custom_prometheus_test.go:32:
The operator seems to be installed correctly but enabling the monitoring fails
This was run against OCP 4.10 and SMCP version 2.4