Bug 1799491 - Azure OLM etcd-operator test is flaky, test is disabled pending debug
Summary: Azure OLM etcd-operator test is flaky, test is disabled pending debug
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.0
Assignee: Kevin Rizza
QA Contact: kuiwang
URL:
Whiteboard:
Depends On:
Blocks: 1806697
TreeView+ depends on / blocked
 
Reported: 2020-02-06 18:02 UTC by Clayton Coleman
Modified: 2020-05-13 21:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1806697 (view as bug list)
Environment:
Last Closed: 2020-05-13 21:56:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24512 0 None closed Bug 1799491: Disable Azure OLM etcd operator test due to flakiness 2020-07-02 12:30:36 UTC
Github openshift origin pull 24594 0 None closed Bug 1799491: Don't instrument etcd operator 2020-07-02 12:30:37 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-13 21:56:46 UTC

Description Clayton Coleman 2020-02-06 18:02:23 UTC
[Feature:Platform] an end user use OLM [Top Level] [Feature:Platform] an end user use OLM can subscribe to the etcd operator [Suite:openshift/conformance/parallel] 

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-4.4/720

fails nearly continuously on azure in 4.4, disabling until someone can identify why.  If this is due to the etcd azure known performance issues (and not some other bug) we should pick a different operator to test or relax the timing constraints.

Disabled on Azure only.

Comment 6 errata-xmlrpc 2020-05-13 21:56:43 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-2020:0581


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