Browse / Deployment Devops / Analyze Prow Job Metal Install Failure

Analyze Prow Job Metal Install Failure

Analyzes OpenShift bare metal installation failures in Prow CI jobs by examining dev-scripts, Ironic, and libvirt log artifacts.

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Differentiates between bootstrap (master) and control-plane (worker) Ironic logs for precise provisioning analysis
  • Checks OFCIR host acquisition logs to identify failures before installation begins
  • Inspects libvirt console logs for VM boot issues and kernel panics
  • Analyzes dev-scripts logs for early-stage setup failures
  • Provides context on network architecture for IPv6 and disconnected environments

Use cases

  • Debugging a failed bare metal CI job with an 'install should succeed' error
  • Investigating why a master or worker node failed to provision in a Metal3/Ironic environment
  • Diagnosing setup failures within the dev-scripts framework before the OpenShift installer runs

FAQ

What does this Claude Code Skill do?

This skill automates the analysis of OpenShift bare metal installation failures in Prow CI jobs. It intelligently examines key artifacts like dev-scripts, Ironic, and libvirt logs to pinpoint the root cause of the failure, from host acquisition to cluster provisioning.

What key analysis capabilities does it provide?

It checks OFCIR logs for pre-installation host acquisition failures, inspects libvirt console logs for VM boot issues, analyzes dev-scripts for early setup problems, and differentiates between bootstrap and control-plane Ironic logs for precise provisioning analysis.

How does this skill improve my workflow?

It significantly speeds up debugging by automatically downloading, extracting, and analyzing complex log sets. Instead of manually sifting through numerous files, you get a targeted analysis that identifies the failure point, saving you valuable time and effort.

When should I use this skill?

Use this skill when a Prow CI job for OpenShift on bare metal (with 'metal' in its name) fails. It's ideal for debugging 'install should succeed' errors, Metal3/Ironic provisioning issues, and failures during the dev-scripts setup phase.