Plans for v3.5.2 release

[serathius]

I think we collected enough bug reports and fixes to v3.5 that we should consider cutting a v3.5.2 release. This issue is meant to propose and track work needed for releasing v3.5.2. I hope that this issue also will make writing changelog simpler. First comment will be used to track list of work.

Backports to be included for v3.5.2:

• [3.5] Set the backend again after recovering v3 backend from snapshot #13501
• storage/backend: Add a gauge to indicate if defrag is active (backport) #13395
• cherry-pick to 3.5 from #13467 exclude the same alarm type activated by multiple peers #13476
• Backport PR 13308 to release-3.5 #13477
• Backport Lease Checkpoints fix to release-3.5 #13515
• fix watchablestore runlock bug #13505
  • backport Backport watchablestore runlock bug fix to release-3.5 #13541

Please feel free to suggest new additional backports/issues worth investigating so we can discuss if they should be included.

Untriaged issues reported for v3.5. Raw list of issues, would appreciate if someone could take a look to make sure that there is no critical bug hiding within them.

Status: All issues triaged

Issues removed from milestone

• Data inconsistency in etcd version 3.5.0 (3.5.x rollback> 3.4 upgrade-> 3.5) story #13514 - removed due to lack of reproduction.
• tcd Version: 3.5.1 watch chan error: etcdserver: no leader  #13510 - looks like performance issue

[serathius]

cc @ptabor @hexfusion @ahrtr @spzala

[ptabor]

Thank you: #13514 looks very serious if is repeatable.

[michaljasionowski]

Backport of watchablestore runlock bug fix: #13541

[serathius]

Thanks for help @michaljasionowski !

[ahrtr]

Thank you: #13514 looks very serious if is repeatable.

The reason of the issue is the etcdctl version is inconsistent with the etcd version. Please se issuecomment-989845565

[ahrtr]

13547 looks like a serious problem, and it could be a valid candidate of etcd v3.5.2.

[serathius]

@ahrtr Thanks for looking into #13541, added it to the plan.

[serathius]

With a specific test on the way and no reproduction I'm inclined to remove #13514 as a blocker for v3.5.2 release.

[serathius]

With actions for v3.5.2 done I think we can start the release process. @hexfusion as a v3.5 release manager, would you be able to take a look? Please let me know if I can assist in any way.

[spzala]

With a specific test on the way and no reproduction I'm inclined to remove #13514 as a blocker for v3.5.2 release.

+1 Thanks for driving this @serathius

[Zamony]

We are waiting for v3.5.2 release too

[serathius]

Waiting for @hexfusion to start the release process. Context: https://groups.google.com/g/etcd-dev/c/6e50-V_LqdQ/m/RNDzSWrWFgAJ?utm_medium=email&utm_source=footer

[hexfusion]

Sorry for the delay I will cut the release this weekend.

[serathius]

v3.5.2 was released