Prow Job Analyze Metal Install Failure

Diagnose OpenShift metal installation failures in Prow CI jobs from logs.

112|305|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/openshift-eng/ai-helpers --skill prow-job-analyze-metal-install-failure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Prow Job Analyze Metal Install Failure
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/prow-job/skills/prow-job-analyze-metal-install-failure
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill prow-job-analyze-metal-install-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gcloud.

What problem does it solve?

This Skill eliminates the guesswork in troubleshooting OpenShift bare metal installation failures in CI environments by systematically analyzing metal-specific artifacts.

Core Features & Use Cases

  • Metal-Specific Diagnostics: Analyzes dev-scripts logs, Ironic provisioning logs, and VM console outputs.
  • Infrastructure Analysis: Detects BMC connectivity issues, provisioning failures, and network configuration problems.
  • Use Case: When a metal CI job fails during installation, use this Skill to pinpoint whether the issue is in host acquisition, dev-scripts setup, Ironic provisioning, or cluster boot sequence.

Quick Start

Use the Prow Job Analyze Metal Install Failure skill to analyze the failed metal CI job at https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_installer/1234/pull-ci-openshift-installer-master-e2e-metal-ipi.

Frequently Asked Questions about Prow Job Analyze Metal Install Failure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why an OpenShift bare metal installation failed in a Prow CI job?

Diagnose bare metal installation failures by analyzing dev-scripts logs, Ironic provisioning logs, and VM console outputs to identify whether the failure occurred during host acquisition, dev-scripts setup, Metal3/Ironic provisioning, or cluster boot. This Skill systematically parses multiple artifact formats and extracts host/provider context to pinpoint the exact failure point with actionable remediation guidance.

What artifacts do I need to debug a metal CI job failure in OpenShift?

Metal CI job failures require dev-scripts logs, OFCIR logs, libvirt console logs, and sosreports. These artifacts contain infrastructure state, provisioning activity, and system diagnostics across the dev-scripts setup, Ironic provisioning, and installer phases, enabling structured diagnosis of BMC connectivity, provisioning, and network configuration issues.

Can this Skill detect BMC connectivity and Ironic provisioning problems?

Yes, this Skill analyzes infrastructure-layer issues including BMC connectivity failures, Metal3/Ironic provisioning failures, and network configuration problems across the provisioning stack. It extracts host and provider context from multiple log formats to identify exactly where the provisioning chain broke.

What's the difference between dev-scripts, Metal3, and Ironic failures in bare metal CI?

Dev-scripts failures occur during host environment setup, Metal3/Ironic failures happen during bare metal provisioning and node acquisition, and installer failures occur during cluster bootstrap. This Skill distinguishes between these layers by parsing layer-specific artifacts—dev-scripts logs, Ironic logs, and console outputs—to isolate which component failed.

Do I need prior knowledge of Prow, dev-scripts, or Ironic to use this Skill?

The Skill handles artifact parsing and failure-point identification; however, you should be familiar with OpenShift bare metal CI workflows, Prow job structure, and the general roles of dev-scripts setup, Metal3/Ironic provisioning, and the OpenShift installer to interpret remediation guidance effectively.

How do I get started analyzing a failed metal CI job?

Locate your failed metal CI job URL in Prow (e.g., https://prow.ci.openshift.org/view/gs/test-platform-results/...), gather the job's dev-scripts logs, Ironic logs, libvirt console outputs, and sosreports, then use this Skill to parse these artifacts and extract structured diagnostics identifying the failure point and remediation steps.