Provision Failure Analysis

Systematic triage of e2e-parallel provision failures in the DEV environment.

Prerequisites

• Required: cihealth-api skill for failure history, run data, and Prow artifacts.
• Conditional: aro-kusto skill for Kubernetes, application, or node evidence that is not present in Prow artifacts.
• DEV Kusto: cluster https://hcp-dev-us-2.eastus2.kusto.windows.net, database ServiceLogs.

ARM and Shell failures can often be fully analyzed from CIHealth, Prow artifacts, pipeline configuration, and source code. Do not require Kusto when those sources already establish the failure.

Step 1: Gather failure data