Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1833250

Summary:	Etcd Operator become Degraded=True while an upgrade is triggered from 4.3.18->4.4.3
Product:	OpenShift Container Platform	Reporter:	Rutvik <rkshirsa>
Component:	Etcd Operator	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED DUPLICATE	QA Contact:	ge liu <geliu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4	CC:	dmace, dyocum, rkshirsa, skolicha, wking, zyu
Target Milestone:	---	Keywords:	Upgrades
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-18 18:29:30 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 Rutvik 2020-05-08 08:13:07 UTC

Description of problem:

Similar to the issue reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1830789

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

How reproducible:
Frequently.

Steps to Reproduce:
1. Upgrade OCP 4.3.18 to 4.4.3 via Fats-4.4 channel
2. Check etcd status, it becomes Degraded and the upgrade would be stuck at 11% and could not move ahead.

Actual results:
- Applied the below workaround as per release notes but could not get through.
~~~
# oc patch etcd cluster -p='{"spec": {"forceRedeploymentReason": "recovery-'"$( date --rfc-3339=ns )"'"}}' --type=merge
~~~

Expected results:
A seamless cluster upgrade without any fail in the operators

Additional info:
Multiple customers are facing a variety of issues the moment they begin with an upgrade. Failure in etcd is pain at this moment.