Skip to content

[release-18.0] Fix RemoveTablet during TabletExternallyReparented causing connection issues (#16371)#16566

Merged
arthurschreiber merged 1 commit intorelease-18.0from
backport-16371-to-release-18.0
Aug 9, 2024
Merged

[release-18.0] Fix RemoveTablet during TabletExternallyReparented causing connection issues (#16371)#16566
arthurschreiber merged 1 commit intorelease-18.0from
backport-16371-to-release-18.0

Conversation

@vitess-bot
Copy link
Contributor

@vitess-bot vitess-bot bot commented Aug 9, 2024

Description

This is a backport of #16371

…tion issues (#16371)

Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
@vitess-bot vitess-bot bot requested a review from deepthi as a code owner August 9, 2024 07:46
@vitess-bot vitess-bot bot added the Backport This is a backport label Aug 9, 2024
@vitess-bot vitess-bot bot requested a review from frouioui as a code owner August 9, 2024 07:46
@vitess-bot vitess-bot bot requested a review from arthurschreiber August 9, 2024 07:46
@vitess-bot
Copy link
Contributor Author

vitess-bot bot commented Aug 9, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@github-actions github-actions bot added this to the v18.0.7 milestone Aug 9, 2024
@arthurschreiber arthurschreiber merged commit 84787fe into release-18.0 Aug 9, 2024
@arthurschreiber arthurschreiber deleted the backport-16371-to-release-18.0 branch August 9, 2024 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant