Description of problem:

When a user chooses to upgrade a multi-arch hosted cluster that was originally deployed with release payload like quay.io/openshift-release-dev/ocp-release:4.13.2-multi, UI chooses quay.io/openshift-release-dev/ocp-release:4.13.9-x86_64 image instead of multi arch image. This causes the upgrade to fail.

As a workaround, the user needs to update the spec.release.image in the hostedcluster and nodepool CRs.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. Create a OCP/MCE cluster with ARM nodes (m6g.xlarge instances)
2. Create a AWS hosted cluster with ARM nodes (m6g.xlarge instances) and select multi-arch OCP 4.13.2 release image
3. On MCE UI, upgrade the hosted cluster to OCP 4.13.9.

Actual results:

The upgrade appears to be hanging on the UI

Expected results:

The upgrade should progress and be completed.

Additional info: