(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:

[sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired architecture should be valid when architecture is set in release payload metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]

Test has a 11.54% pass rate, but 95.00% is required.

Sample (being evaluated) Release: 4.21
Start Time: 2025-11-25T00:00:00Z
End Time: 2025-12-02T16:00:00Z
Success Rate: 11.54%
Successes: 3
Failures: 23
Flakes: 0
Base (historical) Release: 4.20
Start Time: 2025-09-21T00:00:00Z
End Time: 2025-10-21T23:59:59Z
Success Rate: 0.00%
Successes: 0
Failures: 0
Flakes: 0

View the test details report for additional context.

Test seems to fail in many multi jobs, always with same message:

[sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired architecture should be valid when architecture is set in release payload metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel] expand_less 	1s
{  fail [github.com/openshift/origin/test/extended/clusterversion/clusterversion.go:49]: Expected
    <v1.ClusterVersionArchitecture>: 
to equal
    <v1.ClusterVersionArchitecture>: Multi}

Also these tests are mapping to unknown component. They need to get properly mapped. sig-cluster-lifecycle appears to not be sufficient and the preferred current method is the [Jira:"my component"] tag. Alternatively get the ImageStreamImportMode feature gate to map to a component in https://github.com/openshift-eng/ci-test-mapping

Filed by: dgoodwin@redhat.com