Define cluster_profile for e2e test

Signed-off-by: CS Zhang <zhangcho@us.ibm.com>
openshift · Feb 21, 2024 · 72bc88b · 72bc88b
1 parent b49c5a5
commit 72bc88b
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 8 deletions.
diff --git a/ci-operator/config/openshift/multiarch/openshift-multiarch-master__nightly-4.15.yaml b/ci-operator/config/openshift/multiarch/openshift-multiarch-master__nightly-4.15.yaml
@@ -713,6 +713,9 @@ tests:
 - as: ocp-assisted-sno-power
   cron: 0 8 * * 5
   steps:
+    cluster_profile: powervs-3
+    dependencies:
+      OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE: release:ppc64le-latest
     env:
       INSTALL_TYPE: assisted
       OCP_VERSION: "4.15"

diff --git a/ci-operator/step-registry/upi/install/powervs/sno/upi-install-powervs-sno-ref.yaml b/ci-operator/step-registry/upi/install/powervs/sno/upi-install-powervs-sno-ref.yaml
@@ -57,12 +57,6 @@ ref:
       documentation: Name of IBM Cloud CIS instance where DNS records will be created
     - name: CIS_DOMAIN_ID
       documentation: ID of domain created under CIS_INSTANCE
-    - name: CLUSTER_PROFILE_DIR
-      default: ""
-      documentation: Set the default value for e2e when cluster_profile is not defined
-    - name: CLUSTER_TYPE
-      default: "powervs"
-      documentation: Set the default value for e2e when cluster_profile is not defined
   timeout: 3h
   grace_period: 15m
   credentials:

diff --git a/ci-operator/step-registry/upi/powervs/sno/upi-powervs-sno-workflow.yaml b/ci-operator/step-registry/upi/powervs/sno/upi-powervs-sno-workflow.yaml
@@ -18,8 +18,6 @@ workflow:
       CIS_DOMAIN_ID: "9273c1b3cebc817d56b42fc7632a5dfc"
       BASTION: "rh-sno-ci-bastion.ocp-dev-ppc64le.com"
       BASTION_IP: "128.168.100.252"
-      CLUSTER_PROFILE_DIR: "/tmp"
-      CLUSTER_TYPE: "powervs"
   documentation: |-
     upi-powervs-sno workflow will setup a single node openshift cluster via single-node-ignition-config command and ensure it 
     reaches a good state and destroys it.