Skip to content

Add version-pinned nightly testconfigs for OCP 4.21, 4.22, 4.23, and 5.0 on RHOSO#14

Open
tusharjadhav3302 wants to merge 1 commit into
mainfrom
OSPRH-31438-rhoso-ocp-nightly-validation-jobs
Open

Add version-pinned nightly testconfigs for OCP 4.21, 4.22, 4.23, and 5.0 on RHOSO#14
tusharjadhav3302 wants to merge 1 commit into
mainfrom
OSPRH-31438-rhoso-ocp-nightly-validation-jobs

Conversation

@tusharjadhav3302

Copy link
Copy Markdown

Summary

Adds 4 new job definition testconfig files for pre-GA OCP nightly validation on RHOSO 18.0, enabling version-specific regression detection independently of 4-stable.

  • osp_verification_4.21_nightly.yaml — OCP 4.21 nightly
  • osp_verification_4.22_nightly.yaml — OCP 4.22 nightly (explicit coverage after 4-stable rolls forward)
  • osp_verification_4.23_nightly.yaml — OCP 4.23 pre-GA nightly
  • osp_verification_5.0_nightly.yaml — OCP 5.0 pre-GA nightly

Each file is based on osp_verification.yaml with openshift_release pinned to the specific version and openshift_build_name: "" (resolves to latest nightly via the release stream API).

Context

  • The existing osp_verification.yaml uses 4-stable which auto-resolves to the latest stable OCP. These new files supplement it by providing pinned nightly coverage per version.
  • OCP 4.22+ is only supported on RHOSO, so these jobs will run on the RHOSO Zuul periodic pipeline (serval70).
  • Corresponding Zuul job entries will be added in a separate ci-framework-jobs MR.

Related

…5.0 on RHOSO

Co-authored-by: Cursor <cursoragent@cursor.com>
- lb_tests

day2ops_procedures:
- rotate_app_creds

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

rotate_app_creds doesn't exist yet in collection/stages/roles/day2ops/tasks/procedures/ (only moving-etcd-to-ephemeral.yml is there). It's being added in PR #13. The day2ops role does include_tasks: "{{ item }}.yml" over day2ops_steps - so this will fail at runtime if this PR merges first. Worth either ensuring PR #13 goes in first, or removing the day2ops stage until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants