Skip to content

e2e jobs for other repos #1832

Open
1 of 1 issue completed
Open

Description

@kaovilai

cli
nonadmin etc

Activity

  1. changed the title [-]Postsubmit jobs for other repos[/-] [+]Postsubmit e2e jobs for other repos[/+] on Jul 15, 2025
  2. kaovilai commented on Jul 15, 2025

    @kaovilai
    MemberAuthor

    ubi9/10

  3. openshift-bot commented on Oct 14, 2025

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  4. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 14, 2025
  5. openshift-bot commented on Nov 13, 2025

    @openshift-bot

    Stale issues rot after 30d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle rotten.
    Rotten issues close after an additional 30d of inactivity.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle rotten
    /remove-lifecycle stale

  6. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Nov 13, 2025
  7. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    on Nov 13, 2025
  8. changed the title [-]Postsubmit e2e jobs for other repos[/-] [+]e2e jobs for other repos[/+] on Aug 4, 2026
  9. redhat-chai-bot commented on Aug 4, 2026

    @redhat-chai-bot
    Contributor

    Backlog: presubmit e2e coverage for OADP component repos

    Compiled from repos.yaml (the oadp-dev rebase-tooling SSOT) + oadp-operator controller / image-resolution source. Repos are grouped by how each relates to the operator, since that determines the e2e image-substitution approach.

    Prerequisite (done): openshift/release#82762 merged — operator presubmits now build/consume plugin images from the CI registry (namespace: konveyor ImageStreams) instead of quay.io/konveyor. New plugin-repo presubmits substitute into that same path.

    A1 — Velero plugins (own image + DPA *Fqin override; standard backup/restore e2e)

    Repo DPA override key Branches
    openshift/velero veleroImageFqin 1.3→1.6, dev
    openshift/velero-plugin-for-aws awsPluginImageFqin 1.3→1.6, dev
    openshift/velero-plugin-for-gcp gcpPluginImageFqin 1.3→1.6, dev
    openshift/velero-plugin-for-microsoft-azure azurePluginImageFqin 1.3→1.6, dev
    openshift/velero-plugin-for-legacy-aws legacyAWSPluginImageFqin 1.4→1.6, dev
    openshift/openshift-velero-plugin openshiftPluginImageFqin 1.3→1.6, dev
    openshift/velero-plugin-for-csi csiPluginImageFqin 1.3→1.6 *

    Approach: build plugin image from PR → install stock operator (OLMv0 optional-operators-ci-*) → override the one plugin via env/DPA → make test-e2e. Start optional: true + run_if_changed.

    * CSI folded into core Velero upstream (~v1.14) — verify per branch whether CSI still ships a separately-injected image on 1.5/1.6/dev.

    A2 — Operator-reconciled controllers (separate Deployment reconciled by the operator, gated on a DPA feature flag)

    • migtools/oadp-non-admin (nonAdminImageFqin)
    • migtools/kubevirt-datamover-controller — confirmed resolution chain (below); 1.6/dev era
    • vm-file-restore, cli-download, vmdp-download controllers

    Confirmed for datamover (internal/controller/kubevirt_datamover_controller.go, deployment oadp-kubevirt-datamover-controller-manager, gated on the KubeVirtDataMover default plugin):

    // Priority 1: UnsupportedOverrides[KubeVirtDatamoverControllerImageKey]
    // Priority 2: os.Getenv("RELATED_IMAGE_KUBEVIRT_DATAMOVER_CONTROLLER")
    // Priority 3: "quay.io/konveyor/kubevirt-datamover-controller:latest"

    datamover / vm-file-restore / vmdp need a KubeVirt/CNV cluster with a VM workload for meaningful e2e.

    Approach: build PR image → set the controller's RELATED_IMAGE_* (or DPA unsupportedOverrides key) → enable its DPA feature flag → run the targeted suite.

    B — Source-only / go.mod (no standalone injected image; rebuild the consuming image)

    Source repo Rolls up into Override to use
    migtools/kopia velero veleroImageFqin
    openshift/restic velero (bundled binary) veleroImageFqin
    migtools/udistribution openshift-velero-plugin openshiftPluginImageFqin
    migtools/velero-plugin-for-s3 oadp-s3-plugin (built in operator) verify
    migtools/velero-plugin-for-vsphere oadp-vsphere-plugin (built in operator) verify

    Approach: build the consuming image from the PR source (go.mod replace / vendored change), then substitute that image via its RELATED_IMAGE_* key and run operator e2e.

    C — oadp-operator

    Bundle producer; e2e already exists (extended by #82762). Reference implementation the other groups substitute into.

    D — Auxiliary (no DPA injection)

    oadp-must-gather, oadp-cli, oadp-documentation — smoke / unit only.

    Open questions / to verify

    • Exact UnsupportedOverrides ImageKey strings + DPA feature-flag names for each A2 controller (only datamover confirmed; verify non-admin / vm-file-restore / cli-download / vmdp parity — siblings clearly use the RELATED_IMAGE_*-env + default shape, but the UnsupportedOverrides Priority-1 path is confirmed only for datamover).
    • CSI separate-image status per branch (see A1 *).
    • s3 / vsphere override keys (Group B).
    • Whether the e2e framework exposes convenience env vars (e.g. AWS_PLUGIN_IMAGE) vs. setting DPA unsupportedOverrides directly, per branch.

    Related


    AI-generated. Review for accuracy.

  10. 42 remaining items

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.testing

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions