Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _releases/ocp-4.22-test-jobs-amd64.json
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
"upgrade": true
},
{
"prowJob": "periodic-ci-openshift-openshift-tests-private-release-4.22-automated-release-stable-4.22-upgrade-from-stable-4.22-aws-ipi-f999",
"prowJob": "periodic-ci-openshift-openshift-tests-private-release-4.22-automated-release-nightly-4.22-upgrade-from-stable-4.22-aws-ipi-f999",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check if the new nightly upgrade job variant exists in openshift/release

# Search for the new job definition in openshift/release repository
gh api repos/openshift/release/contents/ci-operator/jobs/openshift/openshift-tests-private \
  --jq '.[].name' 2>/dev/null | \
  grep -E 'release-4.22.*nightly-4.22-upgrade-from-stable-4.22' || \
  echo "Job definition not found in main branch"

# Also check recent PRs that might add this job
gh pr list --repo openshift/release \
  --search "nightly-4.22-upgrade-from-stable-4.22 in:title,body" \
  --state all \
  --limit 5 \
  --json number,title,state,mergedAt

Repository: openshift/release-tests

Length of output: 305


🌐 Web query:

nightly-4.22-upgrade-from-stable-4.22 openshift job variant

💡 Result:

The "nightly-4.22-upgrade-from-stable-4.22" appears to be a specific job variant name in OpenShift's Prow CI system for testing upgrades within the 4.22 release stream, such as from a stable 4.22 payload to a nightly 4.22 payload. However, no direct matches for this exact variant were found in search results or job histories. Similar existing job variants include: - nightly-4.22-upgrade-from-stable-4.21-e2e-metal-ovn-single-node-rt-upgrade (e.g., result 1) - periodic-ci-openshift-release-main-nightly-4.22-upgrade-from-stable-4.21-e2e-aws-upgrade-ovn-single-node (e.g., result 12) - ci-4.22-upgrade-from-stable-4.21-e2e-aws-ovn-upgrade (e.g., result 8, 60) - nightly-4.22-upgrade-from-stable-4.21-e2e-metal-ipi-upgrade-ovn-ipv6 (e.g., result 13, 59) These jobs test upgrades from stable 4.21 to nightly 4.22 on platforms like AWS, metal, with OVN networking, single-node, etc. The pattern follows OpenShift CI naming: periodic-ci-[org]-[repo]-[branch]-[variant]-[test], where "nightly-4.22-upgrade-from-stable-4.21-[platform/test]" is common for release validation (e.g., results 3, 16 show upgrades from 4.21 in release tags). OpenShift CI configurations are defined in https://github.com/openshift/release/tree/main/ci-operator/config/openshift/release (result 58), with variants like "nightly-4.22" (result 15). A same-version upgrade job (stable-to-nightly 4.22) may exist for micro-updates or analysis but was not explicitly located. For exact config, check https://config.ci.openshift.org or Prow job history at https://prow.ci.openshift.org/job-history/gs/test-platform-results/jobs?org=openshift-release&repo=main&variant=nightly-4.22-upgrade-from-stable-4.22.

Citations:


🌐 Web query:

openshift/release PR nightly-4.22-upgrade-from-stable-4.22

💡 Result:

No pull request titled or numbered "nightly-4.22-upgrade-from-stable-4.22" exists in the openshift/release repository. The string appears to reference a Prow CI job name pattern used for testing upgrades in OpenShift 4.22 nightly releases, such as "periodic-ci-openshift-release-main-nightly-4.22-upgrade-from-stable-4.21-e2e-aws-ovn-upgrade". These jobs test upgrades from stable-4.21 to nightly 4.22, but no exact match for "from-stable-4.22" was found, likely because intra-version (nightly to stable 4.22) upgrade tests follow different naming or are not standard for the same minor version. OpenShift 4.22 is in active development with ongoing nightly builds as of 2026-04-03, visible in release tags like 4.22.0-0.nightly-2026-03-23-022245 showing upgrade tests from prior 4.22 nightlies and 4.21 stables.

Citations:


🌐 Web query:

openshift-tests-private nightly 4.22 upgrade job

💡 Result:

The "openshift-tests-private nightly 4.22 upgrade job" refers to OpenShift CI nightly testing jobs for version 4.22 that incorporate private or QE (Quality Engineering) extended tests from the openshift-tests-private suite. openshift-tests-private is an internal/private repository containing additional E2E test cases used in OpenShift CI, often migrated to component repositories like cloud-credential-operator for extension testing. No single job is explicitly named "openshift-tests-private nightly 4.22 upgrade job". Instead, relevant nightly upgrade jobs for 4.22 include: - periodic-ci-openshift-release-main-nightly-4.22-upgrade-analysis-all #2029530144976146432: Analyzes upgrade test results across configurations. View logs/artifacts: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-main-nightly-4.22-upgrade-analysis-all/2029530144976146432 - periodic-ci-openshift-release-main-nightly-4.22-upgrade-from-stable-4.21-e2e-aws-upgrade-ovn-single-node #2026423404709548032: Upgrade test from 4.21 to 4.22 on AWS single-node OVN. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-main-nightly-4.22-upgrade-from-stable-4.21-e2e-aws-upgrade-ovn-single-node/2026423404709548032 - periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-vsphere-ovn-upgrade #2026952825568759808: CI upgrade test on vSphere OVN. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-vsphere-ovn-upgrade/2026952825568759808 These jobs run extended tests, including those originating from openshift-tests-private (e.g., CCO tests migrated in openshift/cloud-credential-operator#961). For full job history, search Prow: https://prow.ci.openshift.org/?job=.*4\.22.*upgrade.* or OpenShift CI search: https://search.ci.openshift.org/. Recent 4.22 nightly payloads (e.g., 4.22.0-0.okd-scos-nightly-2026-04-01-024551) show mixed upgrade test results, with some AWS upgrades failing after retries.

Citations:


Verify the new job variant exists before merging.

The PR description states this change depends on an openshift/release PR that adds the new nightly-4.22-upgrade-from-stable-4.22 job variant. This specific job variant was not found in publicly available OpenShift CI Prow job histories or recent pull requests. Merging this configuration change before confirming the job definition exists in openshift/release will cause job execution failures.

Confirm that:

  1. The openshift/release PR adding nightly-4.22-upgrade-from-stable-4.22 has been merged to the main branch
  2. The job variant is visible in the Prow job configuration

The change itself logically improves consistency by using a nightly-specific upgrade variant in the nightly array, but the dependency must be resolved first.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@_releases/ocp-4.22-test-jobs-amd64.json` at line 20, Confirm the referenced
job variant exists before merging: verify the openshift/release PR that
introduces the "nightly-4.22-upgrade-from-stable-4.22" variant has been merged
to main and that the Prow configuration exposes the variant, then either (a)
proceed with this change if the job
"periodic-ci-openshift-openshift-tests-private-release-4.22-automated-release-nightly-4.22-upgrade-from-stable-4.22-aws-ipi-f999"
resolves successfully in Prow job listings, or (b) revert this replacement and
keep the previous stable variant until the openshift/release change is merged
and visible; check the openshift/release PR and the Prow job config to confirm
the variant name "nightly-4.22-upgrade-from-stable-4.22" is present.

"upgrade": true
}
],
Expand Down