microshift-ci:doctor

To diagnose MicroShift CI failures across multiple releases, you can provide a comma-separated list of release versions to consolidate failing jobs, artifacts, root causes, and Jira bug correlations into an HTML report.

Yes, you can correlate existing Jira bugs with failing Prow jobs by running a bug search dry-run during the per-job agent-driven root cause analysis, which embeds matching open bug information directly into the final HTML report.

Yes, you need gsutil and gh installed because deterministic scripts use them to fetch Prow failures, download required CI artifact directories, and aggregate data before root cause analysis begins.

The best way to generate graphs from PCP data is using the deterministic prepare, graph, and finalize scripts, which leverage pcp-export-pcp2json and matplotlib to produce visualizations when PCP data is present in the downloaded artifacts.

Yes, MicroShift CI diagnosis works for both periodic job failure investigations and PR rebase failure triage, accepting release lists to generate one consolidated HTML summary covering both relevant job types.

If CI artifact directories are not aggregated into the final HTML report, it is likely because the deterministic scripts could not locate pre-downloaded artifacts in the computed work directory required for the agent-driven analysis.