Bug 1874524 - [Feature:Platform][Smoke] Managed cluster should ensure pods use downstream images from our release image with proper ImagePullPolicy [Suite:openshift/conformance/parallel] timing out
Summary: [Feature:Platform][Smoke] Managed cluster should ensure pods use downstream i...
Keywords:
Status: CLOSED DUPLICATE of bug 1874856
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.6.0
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard: non-multi-arch
Depends On: 1827863
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-01 14:31 UTC by Brett Tofel
Modified: 2020-09-03 15:27 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1827863
Environment:
Last Closed: 2020-09-03 15:27:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Ben Parees 2020-09-03 15:22:02 UTC
The current failures appear to be tied to the must-gather pod:
https://search.ci.openshift.org/?search=Managed+cluster+should+ensure+pods+use+downstream+images+from+our+release+image+with+proper+ImagePullPolicy&maxAge=48h&context=1&type=bug%2Bjunit&name=%5Erelease&maxMatches=5&maxBytes=20971520&groupBy=job


I assume this is a result of the pod that is created by "oc must-gather" not setting the expected imagepull policy, so setting this to the oc  team.

Either the test should be made tolerant of that particular pod, or oc must-gather should be updated to set the expected policy.

Comment 2 Ben Parees 2020-09-03 15:25:00 UTC
link to sample job:
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-4.6/1301212438615560192

note that in this job it showed up as a flake (the test got rerun and i guess the must-gather pod was gone by the time the second attempt checked)

Comment 3 Ben Parees 2020-09-03 15:27:19 UTC

*** This bug has been marked as a duplicate of bug 1874856 ***


Note You need to log in before you can comment on or make changes to this bug.