This is a clone of issue OCPBUGS-69674. The following is the description of the original issue:
—
(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:

install should succeed: overall

Significant regression detected.
Fishers Exact probability of a regression: 99.95%.
Test pass rate dropped from 98.99% to 93.62%.

Sample (being evaluated) Release: 4.21
Start Time: 2025-12-10T00:00:00Z
End Time: 2025-12-17T12:00:00Z
Success Rate: 93.62%
Successes: 44
Failures: 3
Flakes: 0
Base (historical) Release: 4.20
Start Time: 2025-09-21T00:00:00Z
End Time: 2025-10-21T23:59:59Z
Success Rate: 98.99%
Successes: 197
Failures: 2
Flakes: 0

View the test details report for additional context.

Job is periodic-ci-openshift-multiarch-master-nightly-4.21-ocp-e2e-aws-ovn-multi-day-0-x-a

From the camgi panel, the worker machines are not provisioning:

  errorMessage: "error launching instance: The architecture 'x86_64' of the specified instance type does not match the architecture 'arm64' of the specified AMI. Specify an instance type and an AMI that have matching architectures, and try again. You can use 'describe-instance-types' or 'describe-images' to discover the architecture of the instance type or AMI."
  errorReason: InvalidConfiguration

Only some runs seem to hit this? Two of the failures are this, the third is something else.

In component readiness at a critical time, thus release blocker or SBAR.

Filed by: dgoodwin@redhat.com