Bug 1811992 - Update from 4.3.0 to 4.3.5 fails - etcd-member is in CrashLoopBackOff status
Summary: Update from 4.3.0 to 4.3.5 fails - etcd-member is in CrashLoopBackOff status
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.0
Assignee: Sam Batschelet
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-10 10:52 UTC by Itzik Brown
Modified: 2023-09-14 05:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:19:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github etcd-io etcd pull 11694 0 None closed proxy/grpcproxy: add return on error for metrics handler 2020-06-30 18:56:51 UTC
Github etcd-io etcd pull 11696 0 None closed cherry pick of #11694 on release-3.4 2020-06-30 18:56:51 UTC
Github etcd-io etcd pull 11697 0 None closed cherry pick of #11694 on release-3.3 2020-06-30 18:56:51 UTC
Github openshift etcd pull 44 0 None closed *: bump etcd to v3.4.7 2020-06-30 18:56:52 UTC

Description Itzik Brown 2020-03-10 10:52:39 UTC 
Description of problem:
Trying to update from 4.3.0 to 4.3.5 it's stuck in Working towards 4.3.5: 84% 
complete

Looking at one of the pods etcd-member-ostest the following error is seen:
http: panic serving 10.128.76.163:56112: runtime error: invalid memory address or nil pointer dereference

Version-Release number of the following components:
OSP16 - RHOS_TRUNK-16.0-RHEL-8-20200226.n.1
OCP as mentioned

How reproducible:

Steps to Reproduce:
As described

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag
Comment 1 Scott Dodson 2020-03-10 13:01:02 UTC 
Please file bugs against the component which is failing. Also please provide whatever logs you feel are relevant to the issue.
Comment 3 Michal Fojtik 2020-05-20 10:59:28 UTC 
This bug is actively worked on.
Comment 4 Dan Mace 2020-05-20 15:20:05 UTC 
Sam, I see the linked upstream PRs already merged — is this fixed in the current release?

I also don't actually see any stack traces attached which help understand what the problem was.
Comment 5 Dan Mace 2020-05-20 15:33:18 UTC 
This was fixed in https://github.com/openshift/etcd/pull/44
Comment 9 ge liu 2020-05-22 10:09:44 UTC 
Run several times of upgrade covered 4.3,4.4,4.5, have not hit above issues, close it.
Comment 11 errata-xmlrpc 2020-07-13 17:19:21 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:2409
Comment 12 Red Hat Bugzilla 2023-09-14 05:54:05 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.