CIHealth
<
Single Day: May 20▾
Last 7 Days Weekly: May 18 - May 24 Sprint: May 11 - May 24 Single Day: May 20
Custom time window
> Reset
View JSON API

Environment: STG

Failure patterns: 3 · Failures matched: 3 · Total runs: 2 · 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.
context deadline exceeded
full failure pattern:
context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — seen in 3 prior week(s); active 1 day(s)Show trend detailsMay 14: 0 · May 15: 0 · May 16: 0 · May 17: 0 · May 18: 0 · May 19: 0 · May 20: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to create several HCP clusters in their customer resource group, but not in the same managed resource group1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057028999443386368
ERROR CODE: InvalidRequestContent; detail message Duplicate ARO-HCP cluster <cluster>. An ARO-HCP cluster <cluster> name 'cluster-candidate-4-21-lwfbjc', Azure Subscription ID 'XX...
full failure pattern:
ERROR CODE: InvalidRequestContent; detail message Duplicate ARO-HCP cluster <cluster>. An ARO-HCP cluster <cluster> name 'cluster-candidate-4-21-lwfbjc', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure resource group <resource-group> 'rg-candidate-4-21-cgh878' already exists; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 14: 0 · May 15: 0 · May 16: 0 · May 17: 0 · May 18: 0 · May 19: 0 · May 20: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:109]: Unexpected error:
    <*fmt.wrapError | 0xc00133ac60>: 
    failed to create HCP cluster cluster-candidate-4-21-lwfbjc: failed starting cluster creation "cluster-candidate-4-21-lwfbjc" in resourcegroup="rg-candidate-4-21-cgh878": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-candidate-4-21-cgh878/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-candidate-4-21-lwfbjc
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Duplicate ARO-HCP cluster name. An ARO-HCP cluster with name 'cluster-candidate-4-21-lwfbjc', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure Resource group name 'rg-candidate-4-21-cgh878' already exists"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/complete_cluster_create_multiversion.go:109]: Unexpected error:
    <*fmt.wrapError | 0xc00133ac60>: 
    failed to create HCP cluster cluster-candidate-4-21-lwfbjc: failed starting cluster creation "cluster-candidate-4-21-lwfbjc" in resourcegroup="rg-candidate-4-21-cgh878": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-candidate-4-21-cgh878/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/cluster-candidate-4-21-lwfbjc
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Duplicate ARO-HCP cluster name. An ARO-HCP cluster with name 'cluster-candidate-4-21-lwfbjc', Azure Subscription ID 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', and and Azure Resource group name 'rg-candidate-4-21-cgh878' already exists"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelARO-HCP should be able to perform a control plane and node pool install with OCP candidate channel for 4.211
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2056917934470598656
RevokeCredentialsAndWait timed out after <minutes> minutes; context deadline exceeded
full failure pattern:
RevokeCredentialsAndWait timed out after <minutes> minutes; context deadline exceeded
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsMay 14: 0 · May 15: 0 · May 16: 0 · May 17: 0 · May 18: 0 · May 19: 0 · May 20: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:252]: Unexpected error:
    <*fmt.wrapErrors | 0xc000bcc3c0>: 
    failed waiting for hcpCluster="admin-cred-lifecycle-n6spml" in resourcegroup="admin-credential-lifecycle-test-lk87zw" to finish revoking creds, caused by: timeout '15.000000' minutes exceeded during RevokeCredentialsAndWait for cluster admin-cred-lifecycle-n6spml in resource group admin-credential-lifecycle-test-lk87zw, error: context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/admin_credential_lifecycle.go:252]: Unexpected error:
    <*fmt.wrapErrors | 0xc000bcc3c0>: 
    failed waiting for hcpCluster="admin-cred-lifecycle-n6spml" in resourcegroup="admin-credential-lifecycle-test-lk87zw" to finish revoking creds, caused by: timeout '15.000000' minutes exceeded during RevokeCredentialsAndWait for cluster admin-cred-lifecycle-n6spml in resource group admin-credential-lifecycle-test-lk87zw, error: context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2ebranch-ci-Azure-ARO-HCP-main-e2e-stage-e2e-parallelCustomer should be able to test admin credentials before cluster ready, then full admin credential lifecycle1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2057028999443386368