microshift-dev:analyze-sos-report

Analyze MicroShift SOS reports to identify runtime failures and generate Markdown investigation reports.

7|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-dev-analyze-sos-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microshift-dev:analyze-sos-report
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/microshift-dev/skills/analyze-sos-report
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill microshift-dev-analyze-sos-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly investigate MicroShift runtime failures by extracting and correlating relevant evidence from an SOS report instead of manually scanning logs and manifests.

Core Features & Use Cases

  • Journal and etcd log triage: Searches MicroShift and embedded etcd logs for errors, timeouts, and startup/controller problems.
  • Pod and container forensics: Identifies unhealthy pods and correlates container restarts with current/previous logs.
  • Kubernetes resource and config checks: Reviews Deployments/DaemonSets and effective MicroShift configuration for misconfiguration indicators.
  • Optional Robot Framework correlation: When provided a Robot Framework log.html URL, it correlates failed tests with system events using timestamp alignment.

Quick Start

Run the microshift-dev:analyze-sos-report skill with your extracted SOS report directory path, optionally adding the Robot Framework log.html URL if you have one.

Frequently Asked Questions about microshift-dev:analyze-sos-report

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

FAQPage Schema
How do I analyze a MicroShift SOS report to find root causes for pod failures?

To analyze a MicroShift SOS report for root causes, the skill correlates journal logs, etcd logs, and pod container states to identify runtime failures. It extracts evidence by performing targeted error searches and generates a Markdown report with recommendations.

Can I debug intermittent MicroShift and CRI-O issues from an SOS report?

Yes, you can debug intermittent MicroShift and CRI-O issues from an SOS report. The skill triages journal and embedded etcd logs for errors and timeouts, making it suitable for debugging intermittent failures across MicroShift, CRI-O, and OVN contexts.

How do I map Robot Framework test failures to MicroShift system events?

To map Robot Framework test failures to MicroShift system events, provide a log.html URL alongside the SOS report. The skill correlates failed tests with system events using timestamp alignment to pinpoint the underlying Kubernetes symptoms.

Do I need to manually extract the tar.xz archive before analyzing a remote SOS report?

No, you do not need to manually extract a remote SOS report archive. The skill implements remote .tar.xz download and extraction to /tmp automatically, or it can use a local extracted SOS report directory path.

What Kubernetes resources does SOS report analysis check for MicroShift misconfigurations?

SOS report analysis checks Kubernetes Deployments and DaemonSets along with effective MicroShift configuration to identify misconfiguration indicators. It reviews these manifests alongside container restart logs to correlate unhealthy pods with system errors.