Bug 2030776
| Summary: | e2e-operator always uses quay master images during presubmit tests | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jonathan Dobson <jdobson> |
| Component: | Storage | Assignee: | Jonathan Dobson <jdobson> |
| Storage sub component: | Local Storage Operator | QA Contact: | Wei Duan <wduan> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | high | CC: | aos-bugs, jsafrane |
| Version: | 4.10 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-10 10:40:43 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jonathan Dobson
2021-12-09 17:31:12 UTC
From the following pod info[1], it uses the ci image not upstream one.
"image": "registry.build01.ci.openshift.org/ci-op-0x7p6lit/pipeline@sha256:a0d36c7382267e0b2789066af0fa4de792bbcf64a09f1374a22f62e19889a364",
"imagePullPolicy": "IfNotPresent",
"name": "local-storage-operator",
From the event[2], the ci image is pulled
"lastTimestamp": "2022-03-01T15:02:44Z",
"message": "Successfully pulled image \"registry.build01.ci.openshift.org/ci-op-0x7p6lit/pipeline@sha256:a0d36c7382267e0b2789066af0fa4de792bbcf64a09f1374a22f62e19889a364\" in 5.089955108s",
but a bit strange that the upstream image is also used somewhere? And it is in default ns.
"lastTimestamp": "2022-03-01T15:05:34Z",
"message": "Successfully pulled image \"quay.io/openshift/origin-local-storage-operator\" in 4.443709141s",
"metadata": {
"creationTimestamp": "2022-03-01T15:05:34Z",
"name": "local-storage-operator-577fddbf77-69792.16d84a18cdf8d835",
"namespace": "default",
"resourceVersion": "31264",
"uid": "a38be354-5b2a-462d-9041-cb094e916ac9"
[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_local-storage-operator/327/pull-ci-openshift-local-storage-operator-master-e2e-operator/1498661877167689728/artifacts/e2e-operator/gather-extra/artifacts/pods.json
[2] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_local-storage-operator/327/pull-ci-openshift-local-storage-operator-master-e2e-operator/1498661877167689728/artifacts/e2e-operator/gather-extra/artifacts/events.json
I understand our CI tested in openshift-local-storage ns and I'd like to update status as "Verified".
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069 |