Bug 2069825 - Potential etcd inconsistent revision and data occurs
Summary: Potential etcd inconsistent revision and data occurs
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Dean West
QA Contact: ge liu
Depends On: 2068601
Blocks: 2069830
TreeView+ depends on / blocked
Reported: 2022-03-29 19:17 UTC by Scott Dodson
Modified: 2022-04-12 08:11 UTC (History)
26 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2068601
: 2069830 (view as bug list)
Last Closed: 2022-04-12 08:10:44 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 771 0 None Merged Bug 2069825: turn on initial corruption check 2022-04-01 22:16:36 UTC
Red Hat Knowledge Base (Solution) 6844331 0 None None None 2022-04-07 07:34:10 UTC
Red Hat Knowledge Base (Solution) 6849521 0 None None None 2022-04-07 07:34:10 UTC
Red Hat Product Errata RHBA-2022:1241 0 None None None 2022-04-12 08:11:01 UTC

Comment 1 W. Trevor King 2022-03-29 21:07:44 UTC
Dropping the UpgradeBlocker stuff, since that decision is tracked in the 4.11 bug 2068601, and we don't want folks looking at this bug thinking it's the canonical space for discussing graph-data edges.  This bug is just about getting the initial-corruption check out to 4.10.z.

Comment 2 W. Trevor King 2022-03-29 21:19:11 UTC
More metadata cleanup.  The regression was OpenShift 4.8 to 4.9 (which took etcd from 3.4 to 3.5), so the Regression keyword belongs on the 4.9.z bug 2069830, and not on this 4.10.z bug.

Comment 9 errata-xmlrpc 2022-04-12 08:10:44 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.9 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.