<
Single Day: Jun 3
> Reset
View JSON API

Environment: PROD

Failure patterns: 5 · Failures matched: 5 · 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.
failed to wait for first cluster "<cluster>" to complete creation
full failure pattern:
failed to wait for first cluster "<cluster>" to complete creation
Signal: IndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 2 day(s)
e2e150.00%1 of 2 job runs affectedIndeterminateSignal: Indeterminate — seen in 1 prior week(s); active 2 day(s)Show trend detailsMay 28: 0 · May 29: 0 · May 30: 1 · May 31: 0 · Jun 1: 0 · Jun 2: 0 · Jun 3: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: failed to wait for first cluster "basic-hcp-cluster" to complete creation
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/clusters_sharing_resgroup.go:132]: failed to wait for first cluster "basic-hcp-cluster" to complete creation
Unexpected error:
    <context.deadlineExceededError>: 
    context deadline exceeded
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-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/a2061991328811585536
ERROR CODE: InvalidRequestContent; detail message Version 'openshift-v<version>' doesn't exist; provider Microsoft.RedHatOpenShift
full failure pattern:
ERROR CODE: InvalidRequestContent; detail message Version 'openshift-v<version>' doesn't exist; 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 28: 0 · May 29: 0 · May 30: 0 · May 31: 0 · Jun 1: 0 · Jun 2: 0 · Jun 3: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:704]: failed to create HCP cluster
Unexpected error:
    <*fmt.wrapError | 0xc000d830a0>: 
    failed to create HCP cluster np-dg-minor-rdcsmw: failed starting cluster creation "np-dg-minor-rdcsmw" in resourcegroup="rg-np-dg-minor-rdcsmw-5hf5zr": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-dg-minor-rdcsmw-5hf5zr/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-dg-minor-rdcsmw
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Version 'openshift-v4.21.0-nightly' doesn't exist"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:704]: failed to create HCP cluster
Unexpected error:
    <*fmt.wrapError | 0xc000d830a0>: 
    failed to create HCP cluster np-dg-minor-rdcsmw: failed starting cluster creation "np-dg-minor-rdcsmw" in resourcegroup="rg-np-dg-minor-rdcsmw-5hf5zr": PUT https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-dg-minor-rdcsmw-5hf5zr/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-dg-minor-rdcsmw
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: InvalidRequestContent
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "InvalidRequestContent",
        "message": "Version 'openshift-v4.21.0-nightly' doesn't exist"
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallel-ocp-nightlyCustomer should downgrade a nodepool to a lower minor version from 4.21.zLatest to 4.19.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2062308558187270144
ERROR CODE: MultipleErrorsOccurred; detail code InvalidRequestContent; detail message Invalid value: "4.19.32": cannot downgrade from version 4.21.18 to 4.19.32; provider Microsof...
full failure pattern:
ERROR CODE: MultipleErrorsOccurred; detail code InvalidRequestContent; detail message Invalid value: "4.19.32": cannot downgrade from version 4.21.18 to 4.19.32; 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 28: 0 · May 29: 0 · May 30: 0 · May 31: 0 · Jun 1: 0 · Jun 2: 0 · Jun 3: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:750]: failed to update nodepool npdg-421-419 to downgrade target 4.19.32
Unexpected error:
    <*fmt.wrapError | 0xc000b99d80>: 
    failed to start nodepool "npdg-421-419" update in cluster "np-dg-minor-2j9tl4" resourcegroup="rg-np-dg-minor-2j9tl4-bbdm8h": PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-dg-minor-2j9tl4-bbdm8h/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-dg-minor-2j9tl4/nodePools/npdg-421-419
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: MultipleErrorsOccurred
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "MultipleErrorsOccurred",
        "message": "2 errors occurred",
        "details": [
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.19.32\": invalid node pool version 4.19.32: cannot downgrade from current version 4.21.18",
            "target": "properties.version.id"
          },
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.19.32\": cannot downgrade from version 4.21.18 to 4.19.32",
            "target": "properties.version.id"
          }
        ]
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:750]: failed to update nodepool npdg-421-419 to downgrade target 4.19.32
Unexpected error:
    <*fmt.wrapError | 0xc000b99d80>: 
    failed to start nodepool "npdg-421-419" update in cluster "np-dg-minor-2j9tl4" resourcegroup="rg-np-dg-minor-2j9tl4-bbdm8h": PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-dg-minor-2j9tl4-bbdm8h/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-dg-minor-2j9tl4/nodePools/npdg-421-419
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: MultipleErrorsOccurred
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "MultipleErrorsOccurred",
        "message": "2 errors occurred",
        "details": [
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.19.32\": invalid node pool version 4.19.32: cannot downgrade from current version 4.21.18",
            "target": "properties.version.id"
          },
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.19.32\": cannot downgrade from version 4.21.18 to 4.19.32",
            "target": "properties.version.id"
          }
        ]
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should downgrade a nodepool to a lower minor version from 4.21.zLatest to 4.19.zLatest1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2061991328811585536
ERROR CODE: MultipleErrorsOccurred; detail code InvalidRequestContent; detail message Invalid value: "4.21.17": cannot downgrade from version 4.21.18 to 4.21.17; provider Microsof...
full failure pattern:
ERROR CODE: MultipleErrorsOccurred; detail code InvalidRequestContent; detail message Invalid value: "4.21.17": cannot downgrade from version 4.21.18 to 4.21.17; 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 28: 0 · May 29: 0 · May 30: 0 · May 31: 0 · Jun 1: 0 · Jun 2: 0 · Jun 3: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:619]: failed to update nodepool npdg-4-21 to downgrade target 4.21.17
Unexpected error:
    <*fmt.wrapError | 0xc000f0d060>: 
    failed to start nodepool "npdg-4-21" update in cluster "np-downgrade-9gv25x" resourcegroup="rg-np-downgrade-9gv25x-zbzp5q": PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-downgrade-9gv25x-zbzp5q/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-downgrade-9gv25x/nodePools/npdg-4-21
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: MultipleErrorsOccurred
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "MultipleErrorsOccurred",
        "message": "2 errors occurred",
        "details": [
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.21.17\": invalid node pool version 4.21.17: cannot downgrade from current version 4.21.18",
            "target": "properties.version.id"
          },
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.21.17\": cannot downgrade from version 4.21.18 to 4.21.17",
            "target": "properties.version.id"
          }
        ]
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/nodepool_version_upgrade.go:619]: failed to update nodepool npdg-4-21 to downgrade target 4.21.17
Unexpected error:
    <*fmt.wrapError | 0xc000f0d060>: 
    failed to start nodepool "npdg-4-21" update in cluster "np-downgrade-9gv25x" resourcegroup="rg-np-downgrade-9gv25x-zbzp5q": PATCH https://management.azure.com/subscriptions/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/resourceGroups/rg-np-downgrade-9gv25x-zbzp5q/providers/Microsoft.RedHatOpenShift/hcpOpenShiftClusters/np-downgrade-9gv25x/nodePools/npdg-4-21
    --------------------------------------------------------------------------------
    RESPONSE 400: 400 Bad Request
    ERROR CODE: MultipleErrorsOccurred
    --------------------------------------------------------------------------------
    {
      "error": {
        "code": "MultipleErrorsOccurred",
        "message": "2 errors occurred",
        "details": [
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.21.17\": invalid node pool version 4.21.17: cannot downgrade from current version 4.21.18",
            "target": "properties.version.id"
          },
          {
            "code": "InvalidRequestContent",
            "message": "Invalid value: \"4.21.17\": cannot downgrade from version 4.21.18 to 4.21.17",
            "target": "properties.version.id"
          }
        ]
      }
    }
    --------------------------------------------------------------------------------
    
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallelCustomer should downgrade a nodepool version z-stream downgrade from 4.21.zLatest to 4.21.zPrevious1
Affected runs (1)
Date (UTC)Associated PRProw job
n/a2061991328811585536
VerifyCiliumConnectivityChecks failed: connectivity check failed, not all pods in cilium-connectivity-check namespace are ready: failed to list pods in cilium-connectivity-check n...
full failure pattern:
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: rate: Wait(n=1) would
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 28: 0 · May 29: 0 · May 30: 0 · May 31: 0 · Jun 1: 0 · Jun 2: 0 · Jun 3: 1none
Full failure examples (1)
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:195]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc001110c30>: 
    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: rate: Wait(n=1) would exceed context deadline
    ...
occurred
fail [github.com/Azure/ARO-HCP/test/e2e/cluster_create_complex_cilium_kv.go:195]: failed to run simple web app and connectivity check with cilium CNI
Unexpected error:
    <*errors.joinError | 0xc001110c30>: 
    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: rate: Wait(n=1) would exceed context deadline
    ...
occurred
Contributing tests (1)
Failed AtJobTestSupport
e2eperiodic-ci-Azure-ARO-HCP-main-periodic-prod-e2e-parallel-ocp-nightlyCustomer 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/a2062308558187270144