Bug 1914343
| Summary: | [sig-imageregistry][Feature:ImageTriggers] Annotation trigger reconciles after the image is overwritten [Suite:openshift/conformance/parallel] timeout on s390x | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeremy Poulin <jpoulin> |
| Component: | Multi-Arch | Assignee: | Jeremy Poulin <jpoulin> |
| Status: | CLOSED ERRATA | QA Contact: | Deep Mistry <dmistry> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.7 | CC: | danili |
| Target Milestone: | --- | Keywords: | TestOnly, UpcomingSprint |
| Target Release: | 4.7.0 | ||
| Hardware: | s390x | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-24 15:51:25 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: | |||
Hi Jeremy, will this issue be resolved before the end of this sprint? If not, can we add "UpcomingSprint"? 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633 |
Description of problem: [sig-imageregistry][Feature:ImageTriggers] Annotation trigger reconciles after the image is overwritten [Suite:openshift/conformance/parallel] frequently times out on s390x fail [github.com/openshift/origin/test/extended/images/trigger/annotation.go:53]: Unexpected error: <*errors.errorString | 0xc0002d29b0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred This bug is referencing an image that does not exist for s390x. The error messages don't make this clear, but it appears as though since the image isn't able to be pulled, tagged image is never deployed, and thus the test times out. It is unclear to me how this test ever should have passed, since this image should have crashed immediately upon deployment.