Skip to content

Update pwer-s2s cluster profile configuration - #83153

Draft
Mohit-sharma46 wants to merge 1 commit into
openshift:mainfrom
Mohit-sharma46:power-s2s-cluster-profile
Draft

Update pwer-s2s cluster profile configuration#83153
Mohit-sharma46 wants to merge 1 commit into
openshift:mainfrom
Mohit-sharma46:power-s2s-cluster-profile

Conversation

@Mohit-sharma46

@Mohit-sharma46 Mohit-sharma46 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

The PR updates the OpenShift multiarch nightly CI configurations for 4.22 and 5.0. The ocp-fips-ovn-remote-s2s-libvirt-multi-p-p test now uses the power-s2s cluster profile instead of libvirt-ppc64le-s2s. All other test settings remain unchanged.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 9, 2026
@openshift-ci

openshift-ci Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

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

@Mohit-sharma46

Copy link
Copy Markdown
Contributor Author

/test all

@coderabbitai

coderabbitai Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 831f201b-5fc2-41eb-a83e-f521c550b52c

📥 Commits

Reviewing files that changed from the base of the PR and between 6fd6d16 and 43ada1d.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (2)
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22.yaml
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml

Walkthrough

The FIPS remote s2s libvirt test now uses the power-s2s cluster profile in the nightly 4.22 and 5.0 multiarch configurations. Other test settings remain unchanged.

Changes

Multiarch profile update

Layer / File(s) Summary
Nightly PowerPC profile configuration
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22.yaml, ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
The FIPS remote s2s libvirt test entries now use power-s2s instead of libvirt-ppc64le-s2s.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: ibm-adarsh, neha-dot-yadav

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: updating the cluster profile configuration, although it contains a minor typo in "pwer-s2s".
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 The patch changes only cluster profile values and generated labels; no Ginkgo declarations or dynamic test-name content changed, and the existing target names remain static.
Test Structure And Quality ✅ Passed The commit changes only CI YAML: two cluster-profile values and matching generated job labels; no Ginkgo test code or test lifecycle, wait, or assertion logic changed.
Microshift Test Compatibility ✅ Passed The patch changes only YAML cluster-profile values and generated job labels; it adds no Ginkgo tests or OpenShift API references requiring MicroShift checks.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The diff contains only YAML cluster-profile updates and generated job label changes; it adds no Ginkgo tests or test code requiring SNO compatibility review.
Topology-Aware Scheduling Compatibility ✅ Passed The patch changes only CI cluster-profile fields from libvirt-ppc64le-s2s to power-s2s; it adds no deployment, operator, controller, or pod scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The commit changes only three YAML configuration files to replace the cluster profile; it adds no process-level code or stdout writes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The commit only changes cluster_profile values and generated job labels; it adds no Ginkgo tests, IPv4 assumptions, or external connectivity.
No-Weak-Crypto ✅ Passed The diff only changes cluster profile labels from libvirt-ppc64le-s2s to power-s2s; no MD5, SHA1, DES, RC4, Blowfish, ECB, crypto code, or secret comparisons were added.
Container-Privileges ✅ Passed The PR changes only cluster-profile references and generated job labels; affected Kubernetes job objects contain none of privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscal...
No-Sensitive-Data-In-Logs ✅ Passed The commit only changes cluster profile metadata; no logging code or sensitive values were added, and credential paths remain unchanged.
✨ 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.

@openshift-ci

openshift-ci Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Mohit-sharma46
Once this PR has been reviewed and has the lgtm label, please assign mjturek for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@Mohit-sharma46: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-fips-ovn-remote-s2s-libvirt-multi-p-p N/A periodic Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-fips-ovn-remote-s2s-libvirt-multi-p-p N/A periodic Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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.

@openshift-ci

openshift-ci Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

@Mohit-sharma46: 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.

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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant