Skip to content

cnv/virt-cluster-validate: Install dependency operators and Azure RWX storage - #82726

Open
tiraboschi wants to merge 1 commit into
openshift:mainfrom
tiraboschi:cnv_vcv_depcoverage
Open

cnv/virt-cluster-validate: Install dependency operators and Azure RWX storage#82726
tiraboschi wants to merge 1 commit into
openshift:mainfrom
tiraboschi:cnv_vcv_depcoverage

Conversation

@tiraboschi

@tiraboschi tiraboschi commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Pre-install nmstate, OADP, NHC, and SNR operators via the install-operators step-registry ref on both e2e-azure and e2e-gcp lanes. This reduces test skips (OADP/backup) and warnings (node remediation) that previously fired because these operators were absent.

On Azure, create an azurefile-csi-nfs StorageClass annotated as the default virt class (storageclass.kubevirt.io/is-default-virt-class), enabling the live-migration check that was previously skipped due to RWO-only storage.

Also surface junit-results.xml in CI artifacts for Spyglass rendering.

GCP RWX storage is left for a follow-up: it requires the gcp-filestore-csi-driver-operator subscription, a ClusterCSIDriver object, and a storage-destroy-csi-gcp-filestore post step for cleanup.

Summary by CodeRabbit

  • Configures Azure and GCP validation workflows to install the NMState, OADP, Node Health Check, and Self Node Remediation operators.
  • Configures Azure RWX storage with an azurefile-csi-nfs StorageClass and enables live-migration validation.
  • Enables host-network validation in both workflows.
  • Archives junit-results.xml in both workflows for Spyglass rendering.
  • Defers GCP RWX storage and live-migration validation to a follow-up change.

@openshift-ci
openshift-ci Bot requested review from fabiand and oshoval July 31, 2026 13:13
@coderabbitai

coderabbitai Bot commented Jul 31, 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

Azure and GCP validation workflows install NMState, OADP, Node Health Check, and Self Node Remediation from v4.22 catalogs. Azure configures Azure Files SMB storage and enables host-network and live-migration validation. GCP enables host-network validation. Both workflows archive JUnit results.

Changes

Cloud validation workflows

Layer / File(s) Summary
Azure operator and storage setup
ci-operator/config/openshift-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml
Azure configures four operators, creates a v4.22 CatalogSource, installs the operators, and sets azurefile-csi-smb as the default virtualization class with ReadWriteMany access.
Azure validation execution
ci-operator/config/openshift-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml
Azure enables host-network and live-migration validation and copies JUnit results.
GCP operator and validation setup
ci-operator/config/openshift-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml
GCP configures four operators, creates a v4.22 CatalogSource, installs the operators, enables host-network validation, retains the live-migration exclusion, and copies JUnit results.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: fabiand, oshoval

Sequence Diagram(s)

sequenceDiagram
  participant CloudWorkflow
  participant CatalogSource
  participant OperatorInstallation
  participant Validation
  participant ResultsArchive
  CloudWorkflow->>CatalogSource: Create v4.22 CatalogSource and wait for readiness
  CloudWorkflow->>OperatorInstallation: Install configured operators
  CloudWorkflow->>Validation: Run enabled cloud validation checks
  Validation->>ResultsArchive: Copy JUnit results
Loading
🚥 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 summarizes the main changes: installing dependency operators and configuring Azure RWX storage.
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 PR changes only CI YAML. It adds no Ginkgo It, Describe, Context, or When titles; added CI step identifiers are static.
Test Structure And Quality ✅ Passed The PR changes only one CI YAML file; no Ginkgo test code, It blocks, or cluster-test assertions were added or modified, so these requirements are not applicable.
Microshift Test Compatibility ✅ Passed The pull request changes only a CI YAML configuration file; it adds no Ginkgo tests or test bodies that require MicroShift compatibility review.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The pull request changes only a CI YAML workflow; it adds no Ginkgo tests or test declarations, so this SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The parent diff adds CI operator subscriptions, a CatalogSource, and a StorageClass, but no affinity, spread, selector, toleration, replica, or PDB scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The PR changes only one CI YAML file; it adds shell-step status output but no OTE binary or process-level Go/suite setup stdout writes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The commit changes only one CI YAML file; it adds no Ginkgo e2e tests or test declarations, so this check is not applicable.
No-Weak-Crypto ✅ Passed The only changed file is CI YAML; added commands and data contain no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto, or secret comparisons.
Container-Privileges ✅ Passed The only changed file adds operator refs, CatalogSource, StorageClass, and CI steps; no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root settings appear.
No-Sensitive-Data-In-Logs ✅ Passed Added logs contain only public operator, catalog, storage, and object-count identifiers; no passwords, tokens, keys, PII, hostnames, or customer data are logged.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci

openshift-ci Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tiraboschi

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-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 31, 2026

@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

🤖 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-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml`:
- Around line 39-45: Remove the skip_checking property from every operator entry
in the OPERATORS definitions at
ci-operator/config/openshift-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml
lines 39-45 and lines 153-159, including the Azure and GCP operator entries, so
installation failures stop validation.
🪄 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: 223d21c4-bf74-45b4-a12c-e5ededdb00b4

📥 Commits

Reviewing files that changed from the base of the PR and between b601ca3 and 6e2d012.

📒 Files selected for processing (1)
  • ci-operator/config/openshift-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml

@tiraboschi
tiraboschi force-pushed the cnv_vcv_depcoverage branch from 6e2d012 to b607717 Compare July 31, 2026 13:26
@tiraboschi

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@tiraboschi
tiraboschi force-pushed the cnv_vcv_depcoverage branch from b607717 to 33f621c Compare July 31, 2026 15:14

@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

🤖 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-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml`:
- Line 115: Remove the trailing `|| true` from the storage-class clearing
command so failures from `oc get` or `oc patch` propagate and stop validation.
Update the command around the `oc get storageclass` pipeline while preserving
the existing patch operation and annotation target.
🪄 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: 8f12653f-2324-4458-9308-4965de11272b

📥 Commits

Reviewing files that changed from the base of the PR and between b607717 and 33f621c.

📒 Files selected for processing (1)
  • ci-operator/config/openshift-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml

@tiraboschi

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@tiraboschi
tiraboschi force-pushed the cnv_vcv_depcoverage branch from 33f621c to fe1d09c Compare August 3, 2026 08:15
@tiraboschi

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-cnv-virt-cluster-validate-main-e2e-azure

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

couldn't prepare candidate: couldn't checkout base SHA 502b304842c6523ff9bb96b3ccfc56093eca880f: error checking out "502b304842c6523ff9bb96b3ccfc56093eca880f": exit status 128 fatal: unable to read tree (502b304842c6523ff9bb96b3ccfc56093eca880f)

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-merge-bot

Copy link
Copy Markdown
Contributor

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

@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

🤖 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-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml`:
- Around line 120-133: Update the StorageClass definition to use the name
azurefile-csi-nfs, set parameters.protocol to nfs, and change skuName to the
supported Premium_LRS value. Adjust the StorageProfile wait and patch commands
to reference azurefile-csi-nfs, including the expected provisioner and existing
claim property settings.
🪄 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: 9249b976-ce23-439d-8d4e-f33d9f48095a

📥 Commits

Reviewing files that changed from the base of the PR and between 33f621c and fe1d09c.

📒 Files selected for processing (1)
  • ci-operator/config/openshift-cnv/virt-cluster-validate/openshift-cnv-virt-cluster-validate-main.yaml

@tiraboschi
tiraboschi force-pushed the cnv_vcv_depcoverage branch from fe1d09c to 6b2d989 Compare August 3, 2026 10:26
@tiraboschi

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-cnv-virt-cluster-validate-main-e2e-azure

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

… storage

Pre-install nmstate, OADP, NHC, and SNR operators via the install-operators
step-registry ref on both e2e-azure and e2e-gcp lanes. This reduces test
skips (OADP/backup) and warnings (node remediation) that previously fired
because these operators were absent.

Since OCP 5.0 nightlies may not have all operators in the default
redhat-operators catalog, a custom CatalogSource is created from the
v4.22 redhat-operator-index (the last released OCP version).

On Azure, create an azurefile-csi-nfs StorageClass annotated as the default
virt class (storageclass.kubevirt.io/is-default-virt-class), enabling the
live-migration check that was previously skipped due to RWO-only storage.

Also surface junit-results.xml in CI artifacts for Spyglass rendering.

GCP RWX storage is left for a follow-up: it requires the
gcp-filestore-csi-driver-operator subscription, a ClusterCSIDriver object,
and a storage-destroy-csi-gcp-filestore post step for cleanup.

Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
@tiraboschi
tiraboschi force-pushed the cnv_vcv_depcoverage branch from 6b2d989 to 88fdcb6 Compare August 3, 2026 10:40
@tiraboschi

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-cnv-virt-cluster-validate-main-e2e-azure

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tiraboschi: 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

[REHEARSALNOTIFIER]
@tiraboschi: 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
pull-ci-openshift-cnv-virt-cluster-validate-main-e2e-azure openshift-cnv/virt-cluster-validate presubmit Ci-operator config changed
pull-ci-openshift-cnv-virt-cluster-validate-main-e2e-gcp openshift-cnv/virt-cluster-validate presubmit Ci-operator config changed
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.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant