Bug 2088131 - remove etcd_perf before restore
Summary: remove etcd_perf before restore
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Thomas Jungblut
QA Contact: ge liu
: 2087982 2087985 (view as bug list)
Depends On: 2087983
Blocks: 2087985
TreeView+ depends on / blocked
Reported: 2022-05-18 19:00 UTC by OpenShift BugZilla Robot
Modified: 2022-06-07 13:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-06-07 13:24:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 836 0 None open [release-4.10] Bug 2088131: remove etcd_perf before restore 2022-05-30 11:32:58 UTC
Red Hat Product Errata RHBA-2022:4882 0 None None None 2022-06-07 13:24:51 UTC

Description OpenShift BugZilla Robot 2022-05-18 19:00:37 UTC
+++ This bug was initially created as a clone of Bug #2087983 +++

external contribution by Forlot Romain (claneys)

This commit deletes "etcd_perf" files that could present if someone has ran a fio test under /var/lib/etcd
like specified in the OpenShift docs about the recommended host practices.

As this file is known as non essential, it could be freely deleted by anticipation by the restore pod when
restoring a cluster to a previous state.


Comment 1 Thomas Jungblut 2022-05-19 06:44:49 UTC
*** Bug 2087985 has been marked as a duplicate of this bug. ***

Comment 2 Thomas Jungblut 2022-05-19 13:49:22 UTC
*** Bug 2087982 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2022-06-07 13:24:31 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 (OpenShift Container Platform 4.10.17 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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