From 31bcae0dcf713c22e8eb69e05f5bd08162ea0556 Mon Sep 17 00:00:00 2001 From: Marek Siarkowicz Date: Mon, 16 May 2022 16:02:18 +0200 Subject: [PATCH] Documentation: Publish v3.5 data inconsistency postmortem --- .../postmortems/v3.5-data-inconsistency.md | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/Documentation/postmortems/v3.5-data-inconsistency.md b/Documentation/postmortems/v3.5-data-inconsistency.md index e3365663f..718097657 100644 --- a/Documentation/postmortems/v3.5-data-inconsistency.md +++ b/Documentation/postmortems/v3.5-data-inconsistency.md @@ -4,7 +4,7 @@ |---------|------------| | Authors | serathius@ | | Date | 2022-04-20 | -| Status | draft | +| Status | published | ## Summary @@ -115,18 +115,18 @@ To reflect this action items should have assigned priority: * P1 - Important for long term success of the project. Blocks v3.6 release. * P2 - Stretch goals that would be nice to have for v3.6, however should not be blocking. -| Action Item | Type | Priority | Bug | -|-------------------------------------------------------------------------------------|----------|----------|-------------------------------------------------| -| etcd testing can reproduce historical data inconsistency issues | Prevent | P0 | | -| etcd detects data corruption by default | Detect | P0 | | -| etcd testing is high quality, easy to maintain and expand | Prevent | P1 | https://github.com/etcd-io/etcd/issues/13637 | -| etcd apply code should be easy to understand and validate correctness | Prevent | P1 | | -| Critical etcd features are not abandoned when contributors move on | Prevent | P1 | https://github.com/etcd-io/etcd/issues/13775 | -| etcd is continuously qualified with failure injection | Prevent | P1 | | -| etcd can reliably detect data corruption (hash is linearizable) | Detect | P1 | | -| etcd checks consistency of snapshots sent between leader and followers | Detect | P1 | https://github.com/etcd-io/etcd/issues/13973 | -| etcd recovery from data inconsistency procedures are documented and tested | Mitigate | P1 | | -| etcd can imminently detect and recover from data corruption (implement Merkle root) | Mitigate | P2 | https://github.com/etcd-io/etcd/issues/13839 | +| Action Item | Type | Priority | Bug | +|-------------------------------------------------------------------------------------|----------|----------|----------------------------------------------| +| etcd testing can reproduce historical data inconsistency issues | Prevent | P0 | https://github.com/etcd-io/etcd/issues/14045 | +| etcd detects data corruption by default | Detect | P0 | https://github.com/etcd-io/etcd/issues/14039 | +| etcd testing is high quality, easy to maintain and expand | Prevent | P1 | https://github.com/etcd-io/etcd/issues/13637 | +| etcd apply code should be easy to understand and validate correctness | Prevent | P1 | | +| Critical etcd features are not abandoned when contributors move on | Prevent | P1 | https://github.com/etcd-io/etcd/issues/13775 | +| etcd is continuously qualified with failure injection | Prevent | P1 | | +| etcd can reliably detect data corruption (hash is linearizable) | Detect | P1 | | +| etcd checks consistency of snapshots sent between leader and followers | Detect | P1 | https://github.com/etcd-io/etcd/issues/13973 | +| etcd recovery from data inconsistency procedures are documented and tested | Mitigate | P1 | | +| etcd can imminently detect and recover from data corruption (implement Merkle root) | Mitigate | P2 | https://github.com/etcd-io/etcd/issues/13839 | ## Timeline @@ -138,5 +138,5 @@ To reflect this action items should have assigned priority: | 2021-01-28 | Report of data corruption - https://github.com/etcd-io/etcd/issues/13654 | | 2022-03-08 | Report of data corruption - https://github.com/etcd-io/etcd/issues/13766 | | 2022-03-25 | Corruption confirmed by one of the maintainers - https://github.com/etcd-io/etcd/issues/13766#issuecomment-1078897588 | -| | Statement about the corruption was sent to etcd-dev@googlegroups.com and dev@kubernetes.io | -| | Release v3.5.3 with fix was published - https://github.com/etcd-io/etcd/releases/tag/v3.5.3 | +| 2022-03-29 | Statement about the corruption was sent to etcd-dev@googlegroups.com and dev@kubernetes.io | +| 2022-04-24 | Release v3.5.3 with fix was published - https://github.com/etcd-io/etcd/releases/tag/v3.5.3 |