CIHealth
<
Single Day: May 27▾
Last 7 Days Weekly: May 25 - May 31 Sprint: May 25 - Jun 7 Single Day: May 27
Custom time window
> Reset
View JSON API

Environment: INT

Failure patterns: 4 · Failures matched: 4 · Total runs: 6 · Runs affected: 2

Failure patternThe canonical description of a recurring CI failure, extracted and normalized from raw logs.Failed atThe stage of the job run where this failure occurred: 'provision' (environment setup, DEV only), 'e2e' (test suite execution), or 'other' (CI infrastructure issues that did not produce a failure pattern).Number of distinct job runs where this failure pattern was detected.Percentage of all job runs in this environment affected by this failure pattern during the selected window.Classification of this failure pattern: Regression (likely caused by a specific PR), Flake (intermittent failure spread across days), Noise (low-quality or generic pattern), or Indeterminate.TrendShows daily activity for this failure pattern in a trailing window anchored to the selected end date. The sparkline covers at least 7 days and at most 14 days, depending on the current window size.Also inOther environments where the same failure pattern was also detected during the selected window.
VerifyCiliumConnectivityChecks failed: connectivity check failed, not all pods in cilium-connectivity-check namespace are ready: test pods not yet ready: [echo-b-db89d9c95-khrvb (...
full failure pattern:
VerifyCiliumConnectivityChecks failed: connectivity check failed, not all pods in cilium-connectivity-check namespace are ready: test pods not yet ready: [echo-b-db89d9c95-khrvb (phase: Pending) echo-b-host-95cbd8655-ntvsj (phase: Pending)
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e116.67%1 of 6 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 21: 0 · May 22: 0 · May 23: 0 · May 24: 0 · May 25: 0 · May 26: 0 · May 27: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:211]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc000f1ef90>: 
    VerifyCiliumConnectivityChecks failed: connectivity check failed, not all pods in cilium-connectivity-check namespace are ready: test pods not yet ready: [echo-b-db89d9c95-khrvb (phase: Pending) echo-b-host-95cbd8655-ntvsj (phase: Pending) host-to-b-multi-node-clusterip-c54bf67bf-z8w7b (container host-to-b-multi-node-clusterip-container waiting: CrashLoopBackOff) host-to-b-multi-node-headless-55f66fc4c7-t4gk2 (container host-to-b-multi-node-headless-container waiting: CrashLoopBackOff) pod-to-b-intra-node-nodeport-5884978697-tfxc6 (phase: Pending) pod-to-b-multi-node-clusterip-7d65578cf5-b5f6m (container pod-to-b-multi-node-clusterip-container waiting: CrashLoopBackOff) pod-to-b-multi-node-headless-8557d86d6f-2gkgv (container pod-to-b-multi-node-headless-container waiting: CrashLoopBackOff) pod-to-b-multi-node-nodeport-7847b5df8f-q47xx (container pod-to-b-multi-node-nodeport-container waiting: CrashLoopBackOff)]
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:211]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc000f1ef90>: 
    VerifyCiliumConnectivityChecks failed: connectivity check failed, not all pods in cilium-connectivity-check namespace are ready: test pods not yet ready: [echo-b-db89d9c95-khrvb (phase: Pending) echo-b-host-95cbd8655-ntvsj (phase: Pending) host-to-b-multi-node-clusterip-c54bf67bf-z8w7b (container host-to-b-multi-node-clusterip-container waiting: CrashLoopBackOff) host-to-b-multi-node-headless-55f66fc4c7-t4gk2 (container host-to-b-multi-node-headless-container waiting: CrashLoopBackOff) pod-to-b-intra-node-nodeport-5884978697-tfxc6 (phase: Pending) pod-to-b-multi-node-clusterip-7d65578cf5-b5f6m (container pod-to-b-multi-node-clusterip-container waiting: CrashLoopBackOff) pod-to-b-multi-node-headless-8557d86d6f-2gkgv (container pod-to-b-multi-node-headless-container waiting: CrashLoopBackOff) pod-to-b-multi-node-nodeport-7847b5df8f-q47xx (container pod-to-b-multi-node-nodeport-container waiting: CrashLoopBackOff)]
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2059472048266153984
client rate limiter Wait returned an error: context deadline exceeded
full failure pattern:
client rate limiter Wait returned an error: context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e116.67%1 of 6 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 21: 0 · May 22: 0 · May 23: 0 · May 24: 0 · May 25: 0 · May 26: 0 · May 27: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:211]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc000fd75c0>: 
    VerifyCiliumConnectivityChecks failed: connectivity check failed, not all pods in cilium-connectivity-check namespace are ready: failed to list pods in cilium-connectivity-check namespace: client rate limiter Wait returned an error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:211]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc000fd75c0>: 
    VerifyCiliumConnectivityChecks failed: connectivity check failed, not all pods in cilium-connectivity-check namespace are ready: failed to list pods in cilium-connectivity-check namespace: client rate limiter Wait returned an error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2059569820239663104
configmaps "image-registry-allowlist-config" is forbidden: User "system:serviceaccount:ci-op-2n8rcldp:integration-e2e-parallel" cannot get resource "configmaps" in API group "" in...
full failure pattern:
configmaps "image-registry-allowlist-config" is forbidden: User "system:serviceaccount:ci-op-2n8rcldp:integration-e2e-parallel" cannot get resource "configmaps" in API group "" in the namespace "<namespace>"
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e116.67%1 of 6 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 21: 0 · May 22: 0 · May 23: 0 · May 24: 0 · May 25: 0 · May 26: 0 · May 27: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:144]: ConfigMap image-registry-allowlist-config should exist
Unexpected error:
    <*errors.StatusError | 0xc000e48780>: 
    configmaps "image-registry-allowlist-config" is forbidden: User "system:serviceaccount:ci-op-2n8rcldp:integration-e2e-parallel" cannot get resource "configmaps" in API group "" in the namespace "image-registry-policy"
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/image_registry_policy.go:144]: ConfigMap image-registry-allowlist-config should exist
Unexpected error:
    <*errors.StatusError | 0xc000e48780>: 
    configmaps "image-registry-allowlist-config" is forbidden: User "system:serviceaccount:ci-op-2n8rcldp:integration-e2e-parallel" cannot get resource "configmaps" in API group "" in the namespace "image-registry-policy"
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelImage Registry Policy should allow pods with images from allowed registries and have a valid allowlist1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2059472048266153984
failed to cleanup resource group: at least one HCP cluster <cluster> to delete: failed waiting for hcpcluster="<cluster>" in resourcegroup="<resource-group>" to finish deleting: c...
full failure pattern:
failed to cleanup resource group: at least one HCP cluster <cluster> to delete: failed waiting for hcpcluster="<cluster>" in resourcegroup="<resource-group>" to finish deleting: context canceled
Signal: IndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 1 day(s)
e2e116.67%1 of 6 job runs affectedIndeterminateSignal: Indeterminate — seen in 2 prior week(s); active 1 day(s)Show trend detailsMay 21: 0 · May 22: 0 · May 23: 0 · May 24: 0 · May 25: 0 · May 26: 0 · May 27: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:278] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc001476348>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="np-skip-minor-gjxj7m" in resourcegroup="rg-np-skip-minor-gjxj7m-vmcss2" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:278] A node timeout occurred and then the following failure was recorded in the timedout node before it exited:
Unexpected error:
    <*errors.joinError | 0xc001476348>: 
    failed to cleanup resource group: at least one hcp cluster failed to delete: failed waiting for hcpCluster="np-skip-minor-gjxj7m" in resourcegroup="rg-np-skip-minor-gjxj7m-vmcss2" to finish deleting: context canceled
    ...
occurred  
fail [:0]: A node timeout occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallelCustomer should upgrade a nodepool skipping one minor version (+2) from 4.20.z to 4.22.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2059472048266153984