Skip to content

Add a distinct virt-kdm AWS E2E job for KubeVirt Data Mover presubmits #2399

Description

@coderabbitai

Summary

Create a distinct virtualized E2E CI job for KubeVirt Data Mover (KDM) validation.

The job name must contain virt-kdm. This name differentiates the KDM test from the existing general e2e-test-aws job in openshift/oadp-operator.

Rationale

The KDM controller and KDM plugin presubmits run the OADP operator E2E image with TEST_VIRT_KDM=true. This flag selects only the (kdm) Ginkgo-labeled specifications.

A distinct job name makes the selected suite explicit in CI results. It also prevents confusion with the general OADP operator virtualized E2E job.

Required changes

  • Add or rename the OADP operator AWS virtualized KDM E2E job so that its name contains virt-kdm.
  • Configure the job to run the KDM-only suite with TEST_VIRT_KDM=true.
  • Keep the existing general e2e-test-aws job separate.
  • Update the KDM controller and KDM plugin presubmit configuration to use the KDM-specific job.
  • Apply the change for supported OADP release branches where the KDM presubmits run.
  • Regenerate and validate the affected CI job definitions.

Acceptance criteria

  • CI exposes a job name that contains virt-kdm.
  • The job runs only (kdm)-labeled specifications.
  • The KDM controller and KDM plugin presubmits use the virt-kdm job.
  • The existing general e2e-test-aws job remains available and is not conflated with the KDM suite.
  • Rehearsals confirm the KDM job executes the expected label filter and passes.

Context

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions