Skip to content

[WIP] CMP-4229: Add rhcos10 test for Compliance Operator, File Integrity Operator and SPO#79345

Open
Anna-Koudelkova wants to merge 1 commit into
openshift:mainfrom
Anna-Koudelkova:rhcos10-test
Open

[WIP] CMP-4229: Add rhcos10 test for Compliance Operator, File Integrity Operator and SPO#79345
Anna-Koudelkova wants to merge 1 commit into
openshift:mainfrom
Anna-Koudelkova:rhcos10-test

Conversation

@Anna-Koudelkova
Copy link
Copy Markdown
Contributor

@Anna-Koudelkova Anna-Koudelkova commented May 15, 2026

Add rhcos10 test for Compliance Operator, File Integrity Operator and Security Profiles Operator

Summary

This PR adds RHCOS 10 (Red Hat CoreOS 10) test coverage for the OpenShift 4.22 release's multi-nightly CI pipeline. Specifically, it introduces four new FIPS-enabled test jobs running on GCP infrastructure for the Compliance Operator, File Integrity Operator, and Security Profiles Operator.

Changes

The modification adds test configuration entries to the openshift-tests-private release 4.22 multi-nightly CI jobs. The new test jobs are configured with:

  • RHEL 10 as the base OS image (representing RHCOS 10)
  • FIPS enabled mode for security certification compatibility
  • Tech Preview feature set without upgrades
  • Specific test scenarios and filters tailored for each operator
  • Appropriate test timeouts (30 seconds for compliance and file integrity tests; 55 seconds for compliance with external destinations)

The tests leverage the file-integrity-konflux-catalogsource and configure appropriate test parallelization for each operator's test suite.

Impact

This extends the CI infrastructure's test coverage to validate operator functionality on RHCOS 10, ensuring the Compliance Operator, File Integrity Operator, and Security Profiles Operator work correctly on the newer RHEL 10-based CoreOS platform.

@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 May 15, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 15, 2026

Walkthrough

This PR adds four new FIPS-enabled test cases to the OpenShift release 4.22 multi-nightly CI configuration. The tests target GCP IPI environments with etcd encryption and RHEL 10, running in TechPreviewNoUpgrade mode, with variations for compliance, file-integrity, and security-profiles scenarios.

Changes

FIPS etcd-encryption test configuration

Layer / File(s) Summary
GCP FIPS etcd-encryption test cases for RHEL 10
ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.22__multi-nightly.yaml
Four new test entries for GCP IPI proxy etcd-encryption with FIPS and RHEL 10 are added. Each test configures FEATURE_SET: TechPreviewNoUpgrade, FIPS_ENABLED: "true", OS_IMAGE_STREAM: rhel-10, catalog source references, test filters and scenarios, and parallelism. The compliance, file-integrity, and compliance-dest variants set TEST_TIMEOUT to 30s or 55s; security-profiles omits timeout. All reference the file-integrity-konflux-catalogsource plus openshift-extended-test and openshift-e2e-test-qe-report steps.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

  • dgoodwin
🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
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 PR modifies only CI config YAML, not Ginkgo test code. The custom check applies to test names in test code, not CI job configs.
Test Structure And Quality ✅ Passed PR adds YAML CI workflow configuration only. Custom check targets Ginkgo test code quality, which does not apply to CI configuration files in this repo.
Microshift Test Compatibility ✅ Passed PR adds CI job configuration only, not new Ginkgo test code. Check targets new test code additions, not CI configuration YAML.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR adds only CI job configuration in YAML and does not introduce new Ginkgo e2e tests. The SNO compatibility check applies only to new test implementations.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies CI test configuration only, not deployment manifests or operator code. No topology-aware scheduling constraints introduced.
Ote Binary Stdout Contract ✅ Passed PR only modifies YAML CI configuration file with no source code changes. OTE Binary Stdout Contract check applies to executable code only and is not applicable here.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies only CI/CD YAML configuration. The custom check applies only to Ginkgo e2e test code (It(), Describe(), etc.), which is not present or modified in this PR.
Title check ✅ Passed The title directly describes the main change: adding rhcos10 tests for three operators (Compliance, File Integrity, and SPO), which matches the PR's objective and the YAML configuration additions.

✏️ 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 15, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Anna-Koudelkova
Once this PR has been reviewed and has the lgtm label, please assign tomasdavidorg 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-ci openshift-ci Bot requested review from jechen0648 and memodi May 15, 2026 14:13
@Anna-Koudelkova Anna-Koudelkova changed the title [WIP] Add rhcos10 test for Compliance Operator, File Integrity Operator and SPO [WIP] CMP-4229: Add rhcos10 test for Compliance Operator, File Integrity Operator and SPO May 15, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 15, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 15, 2026

@Anna-Koudelkova: This pull request references CMP-4229 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Add rhcos10 test for Compliance Operator, File Integrity Operator and Security Profiles Operator

Summary

This PR adds RHCOS 10 (Red Hat CoreOS 10) test coverage for the OpenShift 4.22 release's multi-nightly CI pipeline. Specifically, it introduces four new FIPS-enabled test jobs running on GCP infrastructure for the Compliance Operator, File Integrity Operator, and Security Profiles Operator.

Changes

The modification adds test configuration entries to the openshift-tests-private release 4.22 multi-nightly CI jobs. The new test jobs are configured with:

  • RHEL 10 as the base OS image (representing RHCOS 10)
  • FIPS enabled mode for security certification compatibility
  • Tech Preview feature set without upgrades
  • Specific test scenarios and filters tailored for each operator
  • Appropriate test timeouts (30 seconds for compliance and file integrity tests; 55 seconds for compliance with external destinations)

The tests leverage the file-integrity-konflux-catalogsource and configure appropriate test parallelization for each operator's test suite.

Impact

This extends the CI infrastructure's test coverage to validate operator functionality on RHCOS 10, ensuring the Compliance Operator, File Integrity Operator, and Security Profiles Operator work correctly on the newer RHEL 10-based CoreOS platform.

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.

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@Anna-Koudelkova: 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-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance-dest N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-security-profiles N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-file-integrity N/A periodic Periodic 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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.22__multi-nightly.yaml`:
- Around line 3041-3116: The tests block is out of alphabetical order: the four
entries whose as keys start with "gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-"
(e.g., gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance, -compliance-dest,
-file-integrity, -security-profiles) must be moved so they appear after the
existing "gcp-ipi-proxy-..." jobs; relocate those four whole job entries and
ensure the surrounding tests list remains alphabetically ordered by the as key
and that each job’s fields (cron, steps, env, test, workflow) are preserved
exactly.
🪄 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: 6040590a-fc67-4926-95cd-ef2cc45925a9

📥 Commits

Reviewing files that changed from the base of the PR and between 0f686fb and bcda24b.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.22-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.22__multi-nightly.yaml

Comment on lines +3041 to +3116
- as: gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance
cron: 39 3 4 * *
steps:
cluster_profile: gcp-qe
env:
CATALOG_SOURCE_NAME: compliance-operator
COMPUTE_NODE_REPLICAS: "2"
FEATURE_SET: TechPreviewNoUpgrade
FILTERS_ADDITIONAL: ""
FIPS_ENABLED: "true"
OS_IMAGE_STREAM: rhel-10
TEST_FILTERS: ~HyperShiftMGMT&;~DEPRECATED&;~Disruptive&
TEST_PARALLEL: "3"
TEST_SCENARIOS: Compliance_Operator
TEST_TIMEOUT: "30"
test:
- ref: file-integrity-konflux-catalogsource
- ref: openshift-extended-test
- ref: openshift-e2e-test-qe-report
workflow: cucushift-installer-rehearse-gcp-ipi-proxy-etcd-encryption
- as: gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance-dest
cron: 52 1 26 * *
steps:
cluster_profile: gcp-qe
env:
CATALOG_SOURCE_NAME: compliance-operator
COMPUTE_NODE_REPLICAS: "2"
FEATURE_SET: TechPreviewNoUpgrade
FILTERS_ADDITIONAL: ""
FIPS_ENABLED: "true"
OS_IMAGE_STREAM: rhel-10
TEST_FILTERS: ~HyperShiftMGMT&;~StressTest&;~DEPRECATED&;Disruptive&
TEST_PARALLEL: "3"
TEST_SCENARIOS: Compliance_Operator
TEST_TIMEOUT: "55"
test:
- ref: file-integrity-konflux-catalogsource
- ref: openshift-extended-test
- ref: openshift-e2e-test-qe-report
workflow: cucushift-installer-rehearse-gcp-ipi-proxy-etcd-encryption
- as: gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-file-integrity
cron: 31 13 30 * *
steps:
cluster_profile: gcp-qe
env:
FEATURE_SET: TechPreviewNoUpgrade
FILTERS_ADDITIONAL: ""
FIPS_ENABLED: "true"
OS_IMAGE_STREAM: rhel-10
TEST_FILTERS: ~HyperShiftMGMT&;~DEPRECATED&
TEST_PARALLEL: "3"
TEST_SCENARIOS: File_Integrity_Operator
TEST_TIMEOUT: "30"
test:
- ref: file-integrity-konflux-catalogsource
- ref: openshift-extended-test
- ref: openshift-e2e-test-qe-report
workflow: cucushift-installer-rehearse-gcp-ipi-proxy-etcd-encryption
- as: gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-security-profiles
cron: 12 0 4 * *
steps:
cluster_profile: gcp-qe
env:
CATALOG_SOURCE_NAME: security-profiles-operator
FEATURE_SET: TechPreviewNoUpgrade
FILTERS_ADDITIONAL: ""
FIPS_ENABLED: "true"
OS_IMAGE_STREAM: rhel-10
TEST_FILTERS: ~HyperShiftMGMT&;~DEPRECATED&
TEST_PARALLEL: "3"
TEST_SCENARIOS: Security_Profiles_Operator|Node_Audit_Logging
test:
- ref: file-integrity-konflux-catalogsource
- ref: openshift-extended-test
- ref: openshift-e2e-test-qe-report
workflow: cucushift-installer-rehearse-gcp-ipi-proxy-etcd-encryption
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.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Keep tests entries alphabetically sorted by as key.

The new gcp-ipi-px-etcd-enc-* jobs are inserted in the middle of the gcp-ipi-proxy-etcd-encryption-* block (between Line 3041 and Line 3117), which breaks required alphabetical ordering. Please move the four gcp-ipi-px-* entries to their correct sorted position (after all gcp-ipi-proxy-* entries).

As per coding guidelines, "Ensure all jobs are ordered alphabetically".

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.22__multi-nightly.yaml`
around lines 3041 - 3116, The tests block is out of alphabetical order: the four
entries whose as keys start with "gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-"
(e.g., gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance, -compliance-dest,
-file-integrity, -security-profiles) must be moved so they appear after the
existing "gcp-ipi-proxy-..." jobs; relocate those four whole job entries and
ensure the surrounding tests list remains alphabetically ordered by the as key
and that each job’s fields (cron, steps, env, test, workflow) are preserved
exactly.

@Anna-Koudelkova
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@Anna-Koudelkova
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-file-integrity

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 20, 2026

@Anna-Koudelkova: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance bcda24b link unknown /pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-compliance
ci/rehearse/periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-file-integrity bcda24b link unknown /pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-gcp-ipi-px-etcd-enc-rhcos10-tp-fips-amd-f28-file-integrity

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants