Description of Problem: e2e test case: [sig-arch] Managed cluster should ensure pods use downstream images from our release image with proper ImagePullPolicy [Suite:openshift/conformance/parallel] doesn't check all the pods under namespace with 'openshit-' prefix From the e2e job: https://testgrid.k8s.io/redhat-openshift-ocp-release-4.7-informing#release-openshift-ocp-installer-e2e-openstack-4.7 We can see the pods in `openshift-cluster-csi-drivers` did not use the downstream images(https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-4.7/1333229426166468608/artifacts/e2e-openstack/pods.json), but this test case was passed. Version-Release number of selected component (if applicable): How Reproducible: Always Steps to Reproduce: Actual Results: Expected Results: Additional info: Looks like we ignore the namespace wrongly: https://github.com/openshift/origin/blob/master/test/extended/operators/images.go#L166 Except for this, looks like the step to check the image release version is not correct too, we need to define namespace here. https://github.com/openshift/origin/blob/master/test/extended/operators/images.go#L121
> We can see the pods in `openshift-cluster-csi-drivers` Sounds like storage.
*** This bug has been marked as a duplicate of bug 1902552 ***
Hi Martin, It's a different bug from bug 1902552, I reopened it, and created a PR to fix this bug.
(In reply to Qin Ping from comment #4) > Hi Martin, > > It's a different bug from bug 1902552, I reopened it, and created a PR to > fix this bug. Hi Qin, my bad. Thanks for re-opening the bz and the PR.
Setting target to 4.8. Please advise & revert if it's a 4.7 blocker.
Re-assigning to hopefully the correct component. There is an issue in the `[sig-arch] Managed cluster should ensure pods use downstream images [Suite:openshift/conformance/parallel]` test that makes it too permissive. Please see the attached patch https://github.com/openshift/origin/pull/25815.
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira. https://issues.redhat.com/browse/OCPBUGS-8822