Bug 1837157

Summary:	Fix broken test: [sig-etcd][Feature:DisasterRecovery][Disruptive] [Feature:EtcdRecovery] Cluster should restore itself after quorum loss [Serial] [Suite:openshift]
Product:	OpenShift Container Platform	Reporter:	Dan Mace <dmace>
Component:	Etcd	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED DUPLICATE	QA Contact:	ge liu <geliu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5	CC:	ccoleman, skolicha, wking
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-20 12:59:32 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 Dan Mace 2020-05-19 00:39:25 UTC

Description of problem:

https://search.apps.build01.ci.devcluster.openshift.com/chart?search=Cluster+should+restore+itself+after+quorum+loss&maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job

[sig-etcd][Feature:DisasterRecovery][Disruptive] [Feature:EtcdRecovery] Cluster should restore itself after quorum loss [Serial] [Suite:openshift]

This needs fixed or disabled.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dan Mace 2020-05-19 12:33:36 UTC

This test hasn't passed the periodics since March:

https://testgrid.k8s.io/redhat-openshift-ocp-release-4.5-informing#release-openshift-origin-installer-e2e-aws-disruptive-4.5

Comment 2 Dan Mace 2020-05-19 12:42:48 UTC

https://bugzilla.redhat.com/show_bug.cgi?id=1837400 is to cover disabling the broken test, and this bug is to cover fixing it.

Comment 3 Suresh Kolichala 2020-05-20 14:29:23 UTC

*** Bug 1758682 has been marked as a duplicate of this bug. ***

Comment 4 Dan Mace 2020-05-20 20:08:03 UTC

We want to fix this, but it has been failing for months and so clearly the impact hasn't reached a point where we can justify blocking the release. Moving to 4.6.

Comment 5 Sam Batschelet 2020-06-20 12:59:32 UTC


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