Bug 1833250 - Etcd Operator become Degraded=True while an upgrade is triggered from 4.3.18->4.4.3
Summary: Etcd Operator become Degraded=True while an upgrade is triggered from 4.3.18-...
Keywords:
Status: CLOSED DUPLICATE of bug 1830510
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd Operator
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.0
Assignee: Sam Batschelet
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-08 08:13 UTC by Rutvik
Modified: 2023-09-07 23:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-18 18:29:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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