Payload Analysis: {payload

Architecture: {architecture} | Stream: {stream} | Generated: {timestamp}

Release Controller: {payload_tag}

Snapshot: {snapshot_dir}

Executive Summary

Phase: {phase}

{total_blocking} blocking jobs: {succeeded} passed, {failed} failed

{new_failures} new failure(s), {persistent_failures} persistent failure(s)

Chain: {chain_length} payloads, {hours_since_baseline}h since baseline

Consecutive rejections in this stream: {consecutive_rejection_count}

Last accepted: {baseline_tag} ({hours_since_baseline}h ago)

Per-job persistence:

{job_name}: failing {streak_length} consecutive payload(s)

Recommended Reverts

OCP Policy: PRs that break payloads MUST be reverted.

PR	Component	Description	Caused Failure In	Failing Since	Score	Rationale
#{pr_number}	{component}	{description}	{caused_failure_in}	{originating_payload_tag}	{score}	{rationale_with_itemized_signals_separated_by_br}

Automated Reverts

/ci:payload-revert {payload_tag}

Force-Accept Recommended

All blocking job failures are temporary infrastructure issues and no payload has been accepted in this stream for more than 18 hours.

Baseline: {baseline_tag} ({hours_since_baseline}h ago)

Blocking Jobs Summary

Job Name	RHCOS	Status	Streak	History	First Failed In
`{job_name}`	{RHCOS 9\|RHCOS 10\|RHCOS 9+10}	{Passed\|Failed}	{streak_or_na}	{S\|F}	{originating_payload_tag_or_na}

Failed Job Details

Prow Job

Prow | GCS Artifacts{ | Underlying job: underlying_job_name — aggregated jobs only}

This failure is isolated to RHCOS {version} jobs and does not appear in RHCOS {other_version} jobs, indicating an OS-variant-specific root cause (e.g., kernel, systemd, SELinux, or package differences between RHEL 9 and RHEL 10).

Failure Analysis

{analysis_from_subagent}

SHIP Status

{ship_status_line}

Known Symptoms Seen

{comma_separated_symptom_summaries}

First Failed In

{originating_payload_tag}

Candidate PRs (introduced in {originating_payload_tag})

Component	PR	Description	Score
{component}	#{pr_number}	{description}	{score}

Candidate PRs

{why_no_candidate_explains_this_failure}

RHCOS Changes

{one_sentence_rhcos_correlation_summary}

RHCOS RPM Candidates

The following RHCOS package updates scored as regression candidates. These cannot be reverted through the normal PR revert process — escalate to the RHCOS or platform team.

Package	Old Version	New Version	Variant	Score	Affected Jobs	Rationale
{package}	{old_version}	{new_version}	{variant}	{score}	{comma_separated_job_names}	{rationale_with_itemized_signals_separated_by_br}

RPM Changelog Evidence

{package} ({old_version} → {new_version})

{verbatim_changelog_entries}

Full RHCOS RPM Changelog Diffs

{rhcos_name} ({rhcos_tag}) — baseline ({baseline_tag})

Package	Old Version	New Version

{one_line_changelog_theme_summary}

{rhcos_name} ({rhcos_tag}) — hop at {originating_payload_tag}

Package	Old Version	New Version

Informing Test Failures

These tests do not by themselves cause job failures or payload rejections. The only potential impact is if the test itself affects cluster health — for example if it breaks an operator or does something otherwise catastrophic.

Test	Job	Result
`{test_name}`	{job_name}	{result — e.g. "0/9 passes (informing)" or "flake"}

Payload Analysis: {payload_tag}