Bug 1752581 - [GCP] e2e failure: [Feature:Builds][webhook] TestWebhookGitHubPushWithImageStream [Suite:openshift/conformance/parallel]
Summary: [GCP] e2e failure: [Feature:Builds][webhook] TestWebhookGitHubPushWithImageSt...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.0
Assignee: Adam Kaplan
QA Contact: wewang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-16 17:09 UTC by David Eads
Modified: 2019-10-16 06:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:41:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 23802 0 None closed Bug 1752581: Reduce Builds in Webhook Tests 2021-01-05 13:18:42 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:29 UTC

Description David Eads 2019-09-16 17:09:56 UTC
very frequent GCP failures.  If choose to dupe this with general webhook, be aware that will push it to be the single most important GCP bug we have.

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-gcp-4.2/263

Comment 1 Adam Kaplan 2019-09-16 17:38:10 UTC
Flake is due to a timeout tearing down the namespace.

This may reveal a performance degradation for garbage collection on GCP (or at least a lack of parity with AWS).
Each build in 4.2 mounts at minimum two unique ConfigMaps that were not present in 3.11, with appropriate owner-refs to ensure garbage collection on pod deletion.

Comment 3 wewang 2019-09-19 02:16:15 UTC
Verified in version:
4.2.0-0.nightly-2019-09-19-004703

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-gcp-4.2/337

Comment 4 errata-xmlrpc 2019-10-16 06:41:14 UTC
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, 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/RHBA-2019:2922


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