Skip to content

MULTIARCH-6092: Migrate MTO e2e tests from GCP to AWS (v1.x)#80797

Draft
mfbonfigli wants to merge 1 commit into
openshift:mainfrom
mfbonfigli:MULTIARCH-6092-v1x
Draft

MULTIARCH-6092: Migrate MTO e2e tests from GCP to AWS (v1.x)#80797
mfbonfigli wants to merge 1 commit into
openshift:mainfrom
mfbonfigli:MULTIARCH-6092-v1x

Conversation

@mfbonfigli

@mfbonfigli mfbonfigli commented Jun 19, 2026

Copy link
Copy Markdown

Migrate multiarch-tuning-operator e2e tests on v1.x branch to AWS where ARM instances (m6g.xlarge) are more reliably available.

Instance mapping:

  • ARM compute: t2a-standard-4 → m6g.xlarge (4 vCPU, 16GB)
  • x86 worker: n2-standard-4 → m6i.xlarge (4 vCPU, 16GB)

For more details see https://github.com/openshift/release/pull/80580/changes

Note: this should be merged after #80580 as it is based off of that PR branch.

Summary by CodeRabbit

This PR migrates the multiarch-tuning-operator e2e tests from Google Cloud Platform (GCP) to Amazon Web Services (AWS) across the v1.x branch. The migration is necessary because GCP's ARM compute instances (t2a-standard-4) are experiencing regional stockouts in us-central1.

Scope of changes:
The PR updates 10 CI configuration files (5 for openshift/multiarch-tuning-operator and 5 for outrigger-project/multiarch-tuning-operator) covering OCP versions 4.16 through 5.0. Each configuration file has identical changes to its e2e test job definition.

Technical changes:
Each affected configuration replaces the GCP e2e job (e2e-gcp) with an AWS equivalent (e2e-aws) by:

  • Switching the cluster profile from openshift-org-gcp to openshift-org-aws
  • Updating the IPI workflow from ipi-gcp to ipi-aws
  • Mapping VM instance types to AWS equivalents:
    • ARM compute nodes: t2a-standard-4 → m6g.xlarge (both 4 vCPU, 16GB RAM)
    • x86 worker nodes: n2-standard-4 → m6i.xlarge (both 4 vCPU, 16GB RAM)

The changes preserve all test capabilities (arm64 support), skip filters, dependencies, and test references—only the underlying cloud infrastructure and instance sizing are modified.

Dependencies:
This PR depends on PR #80580 and should be merged after that PR is complete.

GCP ARM instances (t2a-standard-4) are unavailable due to regional
stockouts in us-central1. Migrate multiarch-tuning-operator e2e
tests on v1.x branch to AWS where ARM instances (m6g.xlarge) are
more reliably available.

Instance mapping:
- ARM compute: t2a-standard-4 → m6g.xlarge (4 vCPU, 16GB)
- x86 worker: n2-standard-4 → m6i.xlarge (4 vCPU, 16GB)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci

openshift-ci Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot

openshift-ci-robot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

@mfbonfigli: This pull request references MULTIARCH-6092 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Migrate multiarch-tuning-operator e2e tests on v1.x branch to AWS where ARM instances (m6g.xlarge) are more reliably available.

Instance mapping:

  • ARM compute: t2a-standard-4 → m6g.xlarge (4 vCPU, 16GB)
  • x86 worker: n2-standard-4 → m6i.xlarge (4 vCPU, 16GB)

For more details see https://github.com/openshift/release/pull/80580/changes

Note: this should be merged after #80580 as it is based off of that PR branch.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 19, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 19, 2026
@openshift-ci

openshift-ci Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mfbonfigli
Once this PR has been reviewed and has the lgtm label, please assign annazivkovic for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: d3c6d0e1-8b9c-4608-9ee2-45ba8eacd873

📥 Commits

Reviewing files that changed from the base of the PR and between 52c74a1 and 8b09941.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/openshift/multiarch-tuning-operator/openshift-multiarch-tuning-operator-v1.x-presubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/outrigger-project/multiarch-tuning-operator/outrigger-project-multiarch-tuning-operator-v1.x-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (12)
  • ci-operator/config/openshift/multiarch-tuning-operator/openshift-multiarch-tuning-operator-v1.x__ocp416.yaml
  • ci-operator/config/openshift/multiarch-tuning-operator/openshift-multiarch-tuning-operator-v1.x__ocp417.yaml
  • ci-operator/config/openshift/multiarch-tuning-operator/openshift-multiarch-tuning-operator-v1.x__ocp420.yaml
  • ci-operator/config/openshift/multiarch-tuning-operator/openshift-multiarch-tuning-operator-v1.x__ocp421.yaml
  • ci-operator/config/openshift/multiarch-tuning-operator/openshift-multiarch-tuning-operator-v1.x__ocp422.yaml
  • ci-operator/config/openshift/multiarch-tuning-operator/openshift-multiarch-tuning-operator-v1.x__ocp50.yaml
  • ci-operator/config/outrigger-project/multiarch-tuning-operator/outrigger-project-multiarch-tuning-operator-v1.x__ocp416.yaml
  • ci-operator/config/outrigger-project/multiarch-tuning-operator/outrigger-project-multiarch-tuning-operator-v1.x__ocp417.yaml
  • ci-operator/config/outrigger-project/multiarch-tuning-operator/outrigger-project-multiarch-tuning-operator-v1.x__ocp420.yaml
  • ci-operator/config/outrigger-project/multiarch-tuning-operator/outrigger-project-multiarch-tuning-operator-v1.x__ocp421.yaml
  • ci-operator/config/outrigger-project/multiarch-tuning-operator/outrigger-project-multiarch-tuning-operator-v1.x__ocp422.yaml
  • ci-operator/config/outrigger-project/multiarch-tuning-operator/outrigger-project-multiarch-tuning-operator-v1.x__ocp50.yaml

Walkthrough

Across 12 CI operator YAML configuration files for the multiarch-tuning-operator (covering OCP versions 416–422 and 50, under both openshift and outrigger-project orgs), the existing e2e-gcp test job is replaced with an e2e-aws job by updating cluster_profile, workflow, and AWS-specific VM/compute instance type environment variables.

Changes

GCP → AWS e2e job migration for multiarch-tuning-operator

Layer / File(s) Summary
openshift org: e2e-gcp → e2e-aws (ocp416–ocp50)
ci-operator/config/openshift/multiarch-tuning-operator/openshift-multiarch-tuning-operator-v1.x__ocp41{6,7}.yaml, ...ocp42{0,1,2}.yaml, ...ocp50.yaml
Replaces the e2e-gcp test job block with e2e-aws in all six openshift-org OCP variant configs, switching cluster_profile to openshift-org-aws, workflow to ipi-aws, ADDITIONAL_WORKER_VM_TYPE to m6i.xlarge, and COMPUTE_NODE_TYPE to m6g.xlarge.
outrigger-project org: e2e-gcp → e2e-aws (ocp416–ocp50)
ci-operator/config/outrigger-project/multiarch-tuning-operator/outrigger-project-multiarch-tuning-operator-v1.x__ocp41{6,7}.yaml, ...ocp42{0,1,2}.yaml, ...ocp50.yaml
Applies the identical GCP-to-AWS test job replacement across all six outrigger-project OCP variant configs with the same field updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Suggested reviewers

  • jcpowermac
  • aleskandro
🚥 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 accurately describes the main change: migrating multiarch-tuning-operator e2e tests from GCP to AWS for v1.x, which is exactly what all 10 YAML files reflect.
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 PR only modifies CI configuration YAML files to migrate tests from GCP to AWS. No Ginkgo test code files or test definitions were changed, so the stable test names check does not apply.
Test Structure And Quality ✅ Passed PR modifies only YAML CI configuration files in openshift/release repository, not Ginkgo test code. The custom check for test structure quality is not applicable to CI configuration changes.
Microshift Test Compatibility ✅ Passed PR contains only CI/CD YAML infrastructure configuration changes (GCP→AWS migration) with no new Ginkgo e2e test code additions, making the test compatibility check not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR modifies only CI/CD configuration YAML files and does not add any new Ginkgo e2e tests. The check applies only when new tests are added, making it not applicable here.
Topology-Aware Scheduling Compatibility ✅ Passed PR only modifies CI/CD test configuration files (ci-operator/config), not deployment manifests, operator code, or controllers. No scheduling constraints, pod affinity rules, topology spread constra...
Ote Binary Stdout Contract ✅ Passed PR only modifies YAML CI config files; OTE Binary Stdout Contract check applies only to executable code (main, init, TestMain, suite setup, etc.), not configuration.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies only CI configuration YAML files to migrate infrastructure from GCP to AWS. No new Ginkgo e2e tests (It(), Describe(), etc.) are being added, so the check does not apply.
No-Weak-Crypto ✅ Passed This PR only modifies CI/CD YAML configuration files to migrate test infrastructure from GCP to AWS. No cryptographic algorithms, custom crypto implementations, or secret comparison operations are...
Container-Privileges ✅ Passed PR contains no Kubernetes/container manifests with privileged settings. Changes are CI operator config files that define test infrastructure, not container or pod specs.
No-Sensitive-Data-In-Logs ✅ Passed PR adds CI job configuration with no sensitive data exposure; all values are infrastructure parameters (VM types, cluster profiles, image references) appropriate for CI logs.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@mfbonfigli: 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-outrigger-project-multiarch-tuning-operator-v1.x-ocp416-e2e-aws outrigger-project/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-outrigger-project-multiarch-tuning-operator-v1.x-ocp417-e2e-aws outrigger-project/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-outrigger-project-multiarch-tuning-operator-v1.x-ocp420-e2e-aws outrigger-project/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-outrigger-project-multiarch-tuning-operator-v1.x-ocp421-e2e-aws outrigger-project/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-outrigger-project-multiarch-tuning-operator-v1.x-ocp422-e2e-aws outrigger-project/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-outrigger-project-multiarch-tuning-operator-v1.x-ocp50-e2e-aws outrigger-project/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-openshift-multiarch-tuning-operator-v1.x-ocp416-e2e-aws openshift/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-openshift-multiarch-tuning-operator-v1.x-ocp417-e2e-aws openshift/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-openshift-multiarch-tuning-operator-v1.x-ocp420-e2e-aws openshift/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-openshift-multiarch-tuning-operator-v1.x-ocp421-e2e-aws openshift/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-openshift-multiarch-tuning-operator-v1.x-ocp422-e2e-aws openshift/multiarch-tuning-operator presubmit Presubmit changed
pull-ci-openshift-multiarch-tuning-operator-v1.x-ocp50-e2e-aws openshift/multiarch-tuning-operator presubmit Presubmit changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants