OCPBUGS-47700: images: Fix layers test to work with manifestlisted imagestreams

[Prashanth684]

Look at the layers in the submanifest rather than the top level manifest if the imagestream is manifestlisted. Refer to the bug for details.

This fixes techpreview jobs for clusters installed with the multi-payload. Example of a failure: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.19-ocp-e2e-aws-ovn-techpreview-multi-a-a/1873687894279852032

[openshift-ci-robot]

@Prashanth684: This pull request references Jira Issue OCPBUGS-47700, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Look at the layers in the submanifest rather than the top level manifest if the imagestream is manifestlisted. Refer to the bug for details.

This fixes techpreview jobs for clusters installed with the multi-payload. Example of a failure: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.19-ocp-e2e-aws-ovn-techpreview-multi-a-a/1873687894279852032

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.

[flavianmissi]

Test failures seem unrelated.
/retest
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flavianmissi, Prashanth684

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/extended/images/OWNERS [flavianmissi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-trt]

Job Failure Risk Analysis for sha: e6b2fbf

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node	Low [sig-node] static pods should start after being created This test has passed 72.22% of 126 runs on jobs [periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-kube-apiserver-rollout	Low [Conformance][Suite:openshift/kube-apiserver/rollout][Jira:"kube-apiserver"][sig-kube-apiserver] kube-apiserver should roll out new revisions without disruption [apigroup:config.openshift.io][apigroup:operator.openshift.io] This test has passed 50.00% of 6 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:ha Upgrade:none] in the last week.

[Prashanth684]

/retest

[openshift-ci]

New changes are detected. LGTM label has been removed.

[Prashanth684]

@flavianmissi added a change to the logic - we noticed that for clusters of non-x86 architectures running the multi payload, comparing the x86 manifest is not the correct approach - so now each of the submanifest layers are matched to see if one of them match to ensure that it works on any architecture cluster (not just x86).

[Prashanth684]

/test unit

[Prashanth684]

/retest

[openshift-ci]

@Prashanth684: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/unit	1f6155b	link	true	/test unit

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.