CIHealth
<
Single Day: Apr 23▾
Last 7 Days Weekly: Apr 20 - Apr 26 Sprint: Apr 13 - Apr 26 Single Day: Apr 23
Custom time window
> Reset
View JSON API

Environment: STG

Failure patterns: 2 · Failures matched: 2 · Total runs: 3 · 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.
ERROR CODE: ConflictingConcurrentWriteNotAllowed; detail message The operation was interrupted by a conflicting concurrent write on the same entity. Please retry later.; provider ...
full failure pattern:
ERROR CODE: ConflictingConcurrentWriteNotAllowed; detail message The operation was interrupted by a conflicting concurrent write on the same entity. Please retry later.; provider Microsoft.RedHatOpenShift
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e133.33%1 of 3 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsApr 17: 0 · Apr 18: 0 · Apr 19: 0 · Apr 20: 0 · Apr 21: 0 · Apr 22: 0 · Apr 23: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249]: Unexpected error:
    <*errors.joinError | 0xc001647740>: 
    failed to cleanup resource group: ordered cleanup workflow failed for clusternp128-cptdk5: Delete non-networking resources: failed deleting hcp-cluster-np-128/nodepool-128GiB (Microsoft.RedHatOpenShift/HCPOpenShiftClusters/NodePools): DELETE https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/clusternp128-cptdk5/providers/Microsoft.RedHatOpenShift/HCPOpenShiftClusters/hcp-cluster-np-128/NodePools/nodepool-128GiB
    --------------------------------------------------------------------------------
    RESPONSE 409: 409 Conflict
    ERROR CODE: ConflictingConcurrentWriteNotAllowed
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "ConflictingConcurrentWriteNotAllowed",
        "message": "The operation was interrupted by a conflicting concurrent write on the same entity. Please retry later."
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/util/framework/per_test_framework.go:249]: Unexpected error:
    <*errors.joinError | 0xc001647740>: 
    failed to cleanup resource group: ordered cleanup workflow failed for clusternp128-cptdk5: Delete non-networking resources: failed deleting hcp-cluster-np-128/nodepool-128GiB (Microsoft.RedHatOpenShift/HCPOpenShiftClusters/NodePools): DELETE https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/clusternp128-cptdk5/providers/Microsoft.RedHatOpenShift/HCPOpenShiftClusters/hcp-cluster-np-128/NodePools/nodepool-128GiB
    --------------------------------------------------------------------------------
    RESPONSE 409: 409 Conflict
    ERROR CODE: ConflictingConcurrentWriteNotAllowed
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "ConflictingConcurrentWriteNotAllowed",
        "message": "The operation was interrupted by a conflicting concurrent write on the same entity. Please retry later."
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelCustomer should be able to create an HCP cluster and custom node pool osDisk size1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2047133368490921984
MISE Routing routes to the correct frontend based on version header MISE v2 when x-ms-mise-version header is set: assertion failed: expected values to equal
full failure pattern:
MISE Routing routes to the correct frontend based on version header MISE v2 when x-ms-mise-version header is set: assertion failed: expected values to equal
Signal: IndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior history
e2e133.33%1 of 3 job runs affectedIndeterminateSignal: Indeterminate — no prior history; active 1 day(s) — New failure pattern — no prior historyShow trend detailsApr 17: 0 · Apr 18: 0 · Apr 19: 0 · Apr 20: 0 · Apr 21: 0 · Apr 22: 0 · Apr 23: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/mise_routing.go:89]: Expected
    <string>: ...
to equal
    <string>: ...
fail [github.com/Azure/ARO-HCP/test/e2e/mise_routing.go:89]: Expected
    <string>: ...
to equal
    <string>: ...
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-stage-e2e-parallelMISE Routing routes to the correct frontend based on version header MISE v2 when x-ms-mise-version header is set1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2047261708614897664