CIHealth
<
Single Day: May 27▾
Pick a day
>
View JSON API
↗ Open Failure patterns for this day

Environment: INT

Time (UTC)JobFailed atResultPRFailed testsDetails
branch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallel
post-goodmerged PR
No additional run metadata captured
 n/a passed n/a 0 n/a
branch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallel
post-goodmerged PR
No additional run metadata captured
 n/a passed n/a 0 n/a
branch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallel
post-goodmerged PR
No additional run metadata captured
 n/a passed n/a 0 n/a
branch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallel
post-goodmerged PR
No additional run metadata captured
 e2e failed n/a 1
e2e (1)
client rate limiter Wait returned an error: context deadline exceeded
09:38:04 UTC · failed at e2e · test Customer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully · suite integration/parallel
Show raw failure
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
branch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallel
post-goodmerged PR
No additional run metadata captured
 unknown failed n/a 1 non-artifact-backed failure (no junit artifacts)
branch-ci-Azure-ARO-HCP-main-e2e-integration-e2e-parallel
post-goodmerged PR
No additional run metadata captured
 e2e failed n/a 3
e2e (3)
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
03:09:34 UTC · failed at e2e · test Customer should upgrade a nodepool skipping one minor version (+2) from 4.20.z to 4.22.zLatest · suite integration/parallel
Show raw failure
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
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)
03:09:34 UTC · failed at e2e · test Customer should be able to create a no-CNI private cluster with a private key vault, a nodepool and install cilium CNI successfully · suite integration/parallel
Show raw failure
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
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>"
03:09:34 UTC · failed at e2e · test Image Registry Policy should allow pods with images from allowed registries and have a valid allowlist · suite integration/parallel
Show raw failure
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