RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

etcd pod into CrashLoopBackoff with the above error. Possible reason being data directory corrupted/deleted. However the wal files seem intact.   


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

How reproducible:
Happens randomly in the environment. Affecting the production env. 

Steps to Reproduce:
Unable to find a reproducer. We have enabled audit logs on the data directory to identify if any process is causing corruption to the data.  

Additional info:
Removing and adding back the failed existing etcd member solves it.
However, the Cu is pushing us to find the exact reason behind to mitigate the issue.

This bug was resolved upstream and is available via 3.2.28. We will work to get this available to 3.11.

[1] https://github.com/etcd-io/etcd/pull/11308
[2] https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.2.md

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:2115