{}USER STORY:{}

As a OpenShift Engineer, I want to gather e2e signals using native CI step on OCP clusters installed on OCI with Assisted, so I can get results of official e2e conformance suite on an non-integrated provider use case with end-to-end suite using official/supported installation method.

{}DESCRIPTION:{}

SPLAT-1425 introduced the platform type external support to native e2e OCP CI step to allow CI integration and results processing.

Assisted installer already implemented CI steps to provision clusters on OCI with VMs and Barementals.

The goal of this card is to create a workflow reusing provisioning steps from Assisted Installer with VMs[1] (with OPCT) and BMs[2] (custom e2e) to run the official CI e2e conformance step[3], which provides native integration and results post-processing, commonly used in the OCP engineering.

Periodic jobs must be created consuming this workflow to the main stream (4.17) running once a month (budget constraints).

Those[4] are examples of e2e workflows for platform type external (using AWS provider).

[1] https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-assisted-test-infra-master-opct-oci-assisted-periodic

[2] https://github.com/openshift/release/blob/master/ci-operator/step-registry/assisted/oci/assisted-oci-workflow.yaml

[3] openshift-e2e-test https://github.com/openshift/release/blob/master/ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-ref.yaml

[4] https://prow.ci.openshift.org/?job=*e2e-external*

{}Required:{}

• A workflow running openshift-e2e-test step in a cluster provisioned on OCI with Assisted steps, for VMs (maybe BMs if have budget)
• A periodic running once a month using the new workflow in the mainstream (4.17+)

{}Nice to have:{}

• Baremetal job

{}ACCEPTANCE CRITERIA:{}

• PR crated and merged in the release repo introducing periodic to run standard openshift-e2e step on OCI VMs
•  

{}ENGINEERING DETAILS:{}