Fix e2e: Use a 4.20 jobs instead of 4.14 in e2etest

[ngopalak-redhat]

Use 4.20 jobs instead of 4.14 to fix the e2e tests. The old jobs are not available and hence the test failed.

Summary by CodeRabbit

• Chores

  • Updated scheduled release jobs and CI targets from OpenShift 4.14 to 4.20, replacing legacy job entries with their 4.20 equivalents.
  • Updated e2e configuration and view defaults to reference OpenShift 4.20/4.19 as the base/sample release.

• Tests

  • Updated end-to-end setup and seed-data invocation to use OpenShift 4.20.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[ngopalak-redhat]

/test all

[coderabbitai]

Walkthrough

Updated OpenShift release references from 4.14 to 4.20 (and base from 4.13 to 4.19) across e2e configuration, setup scripts, and test constants; replaced three 4.14 job entries with three 4.20 job entries in CI config.

Changes

Cohort / File(s)	Summary
E2E CI config config/e2e-openshift.yaml	Top-level release key changed 4.14 → 4.20; removed three 4.14 job entries and added three corresponding 4.20 job entries (AWS/GCP/Azure job name changes).
E2E views config config/e2e-views.yaml	Updated component_readiness base/sample release fields and name: base_release 4.13 → 4.19, base/sample release references updated to 4.20.
E2E setup scripts e2e-scripts/sippy-e2e-sippy-e2e-setup-commands.sh, scripts/e2e.sh	Updated embedded sippy/load and seed-data invocations to use --release="4.20" instead of 4.14.
Test constants test/e2e/util/e2erequest.go	Updated constants: Release 4.14 → 4.20; BaseRelease 4.13 → 4.19.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 8

✅ Passed checks (8 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main
Go Error Handling	✅ Passed	The pull request modifies only constant values in a Go file without introducing any error handling violations.
Sql Injection Prevention	✅ Passed	Pull request modifies only configuration files, shell scripts, and test utilities with no SQL query construction or database operations present.
Excessive Css In React Should Use Styles	✅ Passed	This custom check is not applicable to the provided pull request. The PR modifies only configuration files (YAML), shell scripts, and Go source files—specifically updating release version numbers from 4.14 to 4.20. None of the modified files are React components (JSX/TSX), and the repository's React components in sippy-ng/src/ are not touched by this PR. Since the check targets excessive inline CSS in React components, which are absent from these changes, the check does not apply.
Single Responsibility And Clear Naming	✅ Passed	PR updates only version constants and configuration values (4.14 to 4.20) without introducing new code entities or violating naming conventions.
Title check	✅ Passed	The title clearly describes the main change: updating e2e test configuration from 4.14 to 4.20 jobs across multiple files.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ngopalak-redhat]

/test e2e

[ngopalak-redhat]

/test all

[ngopalak-redhat]

/test e2e

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@config/e2e-openshift.yaml`:
- Around line 4-8: The listed 4.20 job keys (under the "4.20" map) reference job
names periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial-2of2,
periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial-1of2 and
periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-csi which may not
match the real Prow job names; verify in the OpenShift CI Prow config that these
exact job names exist and are active, and if they do not, replace them with the
correct names (e.g., the actual pattern like
periodic-ci-openshift-release-master-ci-4.20-e2e-*-ovn) or remove them from the
"4.20" map so the mapping only references valid, currently-running Prow jobs.

In `@test/e2e/util/e2erequest.go`:
- Around line 16-17: Tests use Release and BaseRelease constants ("Release" and
"BaseRelease" in e2erequest.go) that don't match any view returned by
ViewsMatchingReleases(); update either the YAML or the constants so the test
queries match an existing view: add a new view entry in e2e-views.yaml with
sample_release="4.20" and base_release="4.19" (e.g., name "4.20-main"), or
change the constants in e2erequest.go to BaseRelease="4.13" and Release="4.14"
to align with the existing "4.14-main" view so ViewsMatchingReleases() returns
data.

🧹 Nitpick comments (1)

scripts/e2e.sh (1)

57-62: Import time may increase significantly with release 4.20.

The comment states older releases are used because they "have very few job runs and thus import quickly, ~5 minutes." Release 4.20 is newer and likely has more job runs, which could substantially increase import time and affect local developer experience.

Consider updating the comment to reflect the expected import time for 4.20, or verify the actual import duration.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

OpenShift CI prow jobs 4.20 e2e-aws-ovn e2e-gcp-ovn

💡 Result:

OpenShift CI (Prow) jobs for OCP 4.20 OVN E2E

• AWS OVN (periodic/blocking on 4.20 nightlies): periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn [1]
• GCP OVN (periodic): periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn [2]

PR (pull) job examples (release-4.20 branch):

• GCP OVN: pull-ci-openshift-origin-release-4.20-e2e-gcp-ovn [3]
• AWS OVN variant found (FIPS): pull-ci-openshift-origin-release-4.20-e2e-aws-ovn-fips [4]

References:
[1] (amd64.ocp.releases.ci.openshift.org)
[2] (prow.ci.openshift.org)
[3] (deck-ci.apps.ci.l2s4.p1.openshiftapps.com)
[4] (deck-ci.apps.ci.l2s4.p1.openshiftapps.com)

Citations:

• 1: https://amd64.ocp.releases.ci.openshift.org/releasetag/4.20.0-0.nightly-2026-01-18-030125?utm_source=openai
• 2: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn/1923562652026540032?utm_source=openai
• 3: https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/test-platform-results/pr-logs/pull/30473/pull-ci-openshift-origin-release-4.20-e2e-gcp-ovn/1988253391788183552?utm_source=openai
• 4: https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/test-platform-results/pr-logs/pull/30295/pull-ci-openshift-origin-release-4.20-e2e-aws-ovn-fips/1970706184457424896?utm_source=openai

---

🏁 Script executed:

# Search the codebase for references to these job names or similar patterns
rg "periodic-ci-openshift-release-master-nightly-4\.(20|14)" --type yaml -A 2 -B 2

Repository: openshift/sippy

Length of output: 458

---

🏁 Script executed:

# Check if there's a job configuration or registry in the codebase
fd -e yaml -e json | xargs grep -l "periodic-ci-openshift-release.*4\.(14|20)" 2>/dev/null | head -20

Repository: openshift/sippy

Length of output: 41

---

Verify job names match actual OpenShift CI Prow configuration.

The job names reference master-nightly variants with -serial-2of2, -serial-1of2, and -csi suffixes, but OpenShift CI 4.20 OVN jobs appear to follow the pattern periodic-ci-openshift-release-master-ci-4.20-e2e-*-ovn without these suffixes. Confirm these specific job name variants (periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial-2of2, periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial-1of2, and periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-csi) exist in Prow configuration and are actively running.

🤖 Prompt for AI Agents

In `@config/e2e-openshift.yaml` around lines 4 - 8, The listed 4.20 job keys
(under the "4.20" map) reference job names
periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial-2of2,
periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial-1of2 and
periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-csi which may not
match the real Prow job names; verify in the OpenShift CI Prow config that these
exact job names exist and are active, and if they do not, replace them with the
correct names (e.g., the actual pattern like
periodic-ci-openshift-release-master-ci-4.20-e2e-*-ovn) or remove them from the
"4.20" map so the mapping only references valid, currently-running Prow jobs.

[ngopalak-redhat]

/test e2e

[ngopalak-redhat]

/test e2e

[ngopalak-redhat]

/test e2e

[openshift-ci]

@ngopalak-redhat: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[neisw]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neisw, ngopalak-redhat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [neisw]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment