Skip to content

OCM-23812: Migrate cs-rosa-hcp-upgrade-staging-main OCM FVT job to Prow periodic - #78591

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
tinaafitz:ocm-23812-migrate-cs-rosa-hcp-upgrade-staging
May 27, 2026
Merged

OCM-23812: Migrate cs-rosa-hcp-upgrade-staging-main OCM FVT job to Prow periodic#78591
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
tinaafitz:ocm-23812-migrate-cs-rosa-hcp-upgrade-staging

Conversation

@tinaafitz

@tinaafitz tinaafitz commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

Migrate cs-rosa-hcp-upgrade-staging-main OCM FVT job to Prow periodic

This PR adds a new periodic Prow CI job to the OpenShift release repository's CI definitions for OpenShift Online Rosa E2E tests. The change lives in ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-staging.yaml and introduces the ocm-fvt-periodic-cs-rosa-hcp-upgrade-staging-main job.

Practical impact:

  • Schedules the OCM Functional Verification Test (FVT) for the ROSA Hosted Control Plane (HCP) "upgrade staging" scenario as a daily Prow periodic job (cron: 0 9 * * *).
  • Runs using the nested-podman pattern (container from base image nested-podman) and executes quay.io/redhat-services-prod/ocmci/ocmci:latest ocmtest test --service cms --job cs-rosa-hcp-upgrade-staging-main --reportJiraTicket.
  • Securely prepares container environment via a temporary podman env file (mktemp), sets restrictive umask (077), and registers a trap to remove the temp file on EXIT.
  • Exposes credential files by mounting the cs-qe-credentials secret at /usr/local/cs-qe-credentials, sets AWS credential environment variables (AWS_SHARED_CREDENTIALS_FILE and SHARED_VPC_AWS_SHARED_CREDENTIALS_FILE), sources ocm-tokens and jira-cred, and enables Jira reporting with a JOB_LINK that mirrors other OCM FVT jobs.
  • Follows the established pattern used by sibling periodic OCM FVT jobs in the same config area; scoped to CI configuration only (no code/public API changes).

Scope: CI configuration for OpenShift Online Rosa E2E within the openshift/release repo — adds a scheduled periodic job to run the existing OCM FVT test in a Prow periodic context.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 29, 2026
@openshift-ci-robot

openshift-ci-robot commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

@tinaafitz: This pull request references OCM-23812 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Migrate cs-rosa-hcp-upgrade-staging-main OCM FVT job to Prow periodic

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 openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Added a new scheduled CI test job ocm-fvt-periodic-cs-rosa-hcp-upgrade-staging-main to the OpenShift Online Rosa e2e config; it runs ocmci/ocmtest under nested-podman, mounts cs-qe-credentials, constructs JOB_LINK, uses a temp-file-based podman env injection, and is scheduled at 0 9 * * *.

Changes

Periodic CS Rosa HCP Upgrade Job

Layer / File(s) Summary
Test Declaration
ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-staging.yaml
Inserted new tests entry ocm-fvt-periodic-cs-rosa-hcp-upgrade-staging-main.
Execution Mode
ci-operator/config/...__ocm-fvt-rosa-hcp-staging.yaml
Sets nested_podman: true and runs the quay.io/redhat-services-prod/ocmci/ocmci:latest container via podman to invoke ocmtest test --service cms with job cs-rosa-hcp-upgrade-staging-main.
Environment / Credentials Wiring
ci-operator/config/...__ocm-fvt-rosa-hcp-staging.yaml
Generates a secure temporary podman env file (mktemp, umask 077), writes podman env vars, sets an EXIT trap to cleanup, and mounts the cs-qe-credentials secret into /usr/local/cs-qe-credentials.
JOB_LINK & Reporting
ci-operator/config/...__ocm-fvt-rosa-hcp-staging.yaml
Builds JOB_LINK conditional on PULL_NUMBER vs non-PR runs and enables Jira reporting (--reportJiraTicket) with ocmtest using sourced ocm-tokens and jira-cred.
Scheduling
ci-operator/config/...__ocm-fvt-rosa-hcp-staging.yaml
Adds cron schedule 0 9 * * * for periodic execution.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: migrating a CI job (cs-rosa-hcp-upgrade-staging-main) to Prow periodic execution, which directly matches the YAML configuration addition in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed This PR modifies CI operator YAML config files, not Ginkgo test definitions. The check applies only to Ginkgo test code. No Ginkgo tests are in the modified files.
Test Structure And Quality ✅ Passed The PR only adds CI operator configuration files (YAML), not Ginkgo test code. The check for Ginkgo test quality is not applicable to CI configuration changes.
Microshift Test Compatibility ✅ Passed This PR only modifies CI configuration files (YAML Prow job definitions), not Ginkgo test code. The check applies only when new Ginkgo e2e tests are added, which is not the case here.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR adds no new Ginkgo e2e tests. It only updates CI configuration for a Prow periodic job. SNO compatibility check not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR adds a CI test config file. Not applicable to topology-aware scheduling check which targets deployment manifests, operators, and controllers deployed to clusters.
Ote Binary Stdout Contract ✅ Passed The OTE Binary Stdout Contract check is for Go code violations. This PR modifies only CI configuration YAML for an E2E test job, containing no Go code changes. Not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies a CI operator configuration YAML file, not Ginkgo e2e test source code. The custom check applies only to Ginkgo test additions. No test code with IPv4 assumptions was added.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci
openshift-ci Bot requested review from bmeng and dustman9000 April 29, 2026 20:10

@coderabbitai coderabbitai Bot left a comment

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.

Actionable comments posted: 1

🧹 Nitpick comments (1)
ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main.yaml (1)

111-112: Prefer an immutable ocmci image reference for reproducible periodic runs.

Using :latest on Line 111 makes job behavior drift over time. Pin to a versioned tag or digest to stabilize debugging and rollback.

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

In
`@ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main.yaml`
around lines 111 - 112, The job uses a floating image tag
"quay.io/redhat-services-prod/ocmci/ocmci:latest" which can drift; replace this
with an immutable, versioned tag or digest (for example a specific semver tag or
sha256 digest) so the periodic run is reproducible—update the image reference in
the job invocation that runs "ocmtest test --service cms --job
cs-rosa-hcp-upgrade-staging-main --reportJiraTicket" to point at the chosen
pinned tag/digest.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main.yaml`:
- Around line 89-104: The heredoc that generates /tmp/podman.env using "env -i
bash --norc --noprofile << 'EOF' ... EOF" can mask failures of the two source
commands (source /usr/local/cs-qe-credentials/ocm-tokens and source
/usr/local/cs-qe-credentials/jira-cred); modify the heredoc to enable fail-fast
by adding a strict shell header (set -euo pipefail) at its start or by appending
explicit checks after each source (e.g., source ... || { echo "failed to source
ocm-tokens"; exit 1; }) so that any sourcing error causes the heredoc to exit
non‑zero and prevent writing an incomplete /tmp/podman.env; apply the same
change to the duplicate heredoc used in the
ocm-fvt-periodic-cs-rosa-hcp-ad-staging-main job.

---

Nitpick comments:
In
`@ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main.yaml`:
- Around line 111-112: The job uses a floating image tag
"quay.io/redhat-services-prod/ocmci/ocmci:latest" which can drift; replace this
with an immutable, versioned tag or digest (for example a specific semver tag or
sha256 digest) so the periodic run is reproducible—update the image reference in
the job invocation that runs "ocmtest test --service cms --job
cs-rosa-hcp-upgrade-staging-main --reportJiraTicket" to point at the chosen
pinned tag/digest.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: a901a003-3166-444d-915d-5cc9f8f528fa

📥 Commits

Reviewing files that changed from the base of the PR and between f5bbc60 and 4bab283.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main.yaml

Comment thread ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main.yaml Outdated
@tinaafitz tinaafitz changed the title draft: OCM-23812: Migrate cs-rosa-hcp-upgrade-staging-main OCM FVT job to Prow periodic OCM-23812: Migrate cs-rosa-hcp-upgrade-staging-main OCM FVT job to Prow periodic Apr 30, 2026
@tinaafitz

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ocm-fvt-periodic-cs-rosa-hcp-upgrade-staging-main

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tinaafitz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tinaafitz: job(s): ocm-fvt-periodic-cs-rosa-hcp-upgrade-staging-main either don't exist or were not found to be affected, and cannot be rehearsed

@tinaafitz
tinaafitz force-pushed the ocm-23812-migrate-cs-rosa-hcp-upgrade-staging branch from 5b0409b to 1cb3776 Compare April 30, 2026 15:39
@tinaafitz

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-online-rosa-e2e-main-ocm-fvt-periodic-cs-rosa-hcp-upgrade-staging-main

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tinaafitz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tinaafitz

Copy link
Copy Markdown
Contributor Author

/retest

@dustman9000

Copy link
Copy Markdown
Member

/lgtm

@dustman9000

Copy link
Copy Markdown
Member

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 4, 2026
@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels May 4, 2026
@tinaafitz
tinaafitz force-pushed the ocm-23812-migrate-cs-rosa-hcp-upgrade-staging branch from 1cb3776 to fc62c7d Compare May 6, 2026 14:50
@openshift-ci openshift-ci Bot removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. lgtm Indicates that a PR is ready to be merged. labels May 6, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tinaafitz, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not determine changed registry steps: could not load step registry: load cluster profile list: unmarshal file /var/tmp/gitrepo775220565/ci-operator/step-registry/cluster-profiles/cluster-profiles-config.yaml: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal array into Go value of type api.ClusterProfilesList
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@tinaafitz

Copy link
Copy Markdown
Contributor Author

/retest

@dustman9000

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 6, 2026
@tinaafitz

Copy link
Copy Markdown
Contributor Author

/test ordered-prow-config

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tinaafitz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@dustman9000

Copy link
Copy Markdown
Member

/lgtm
/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 21, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2026
@tinaafitz

Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 3f4f815 and 2 for PR HEAD 0b9d3b3 in total

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0530848 and 1 for PR HEAD 0b9d3b3 in total

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 7b626c9 and 0 for PR HEAD 0b9d3b3 in total

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/hold

Revision 0b9d3b3 was retested 3 times: holding

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 25, 2026
@tinaafitz
tinaafitz force-pushed the ocm-23812-migrate-cs-rosa-hcp-upgrade-staging branch from 0b9d3b3 to d83bedf Compare May 27, 2026 17:19
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label May 27, 2026
@dustman9000

Copy link
Copy Markdown
Member

/lgtm
/hold cancel

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels May 27, 2026
@openshift-ci

openshift-ci Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustman9000, tinaafitz

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:

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

@openshift-merge-bot
openshift-merge-bot Bot merged commit cf20118 into openshift:main May 27, 2026
15 of 16 checks passed
krisnababu pushed a commit to oharan2/release that referenced this pull request Jul 3, 2026
andrej1991 pushed a commit to andrej1991/release that referenced this pull request Jul 6, 2026
TimurMP pushed a commit to TimurMP/release that referenced this pull request Jul 8, 2026
SachinNinganure pushed a commit to SachinNinganure/release that referenced this pull request Jul 20, 2026
srivickynesh pushed a commit to srivickynesh/release that referenced this pull request Aug 5, 2026
malingatembo pushed a commit to malingatembo/release that referenced this pull request Aug 5, 2026
TimurMP pushed a commit to TimurMP/release that referenced this pull request Sep 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants