*: force the new upgrading tidb to be owner

[wjhuang2016]

What problem does this PR solve?

Issue Number: close #57185

Problem Summary:
force the new upgrading tidb to be owner, so that owner can always use the new code during upgrade,

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[codecov]

Codecov Report

Attention: Patch coverage is 58.66667% with 31 lines in your changes missing coverage. Please review.

Project coverage is 71.9117%. Comparing base (165c4a5) to head (f32b950).
Report is 22 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51285        +/-   ##
================================================
- Coverage   73.4181%   71.9117%   -1.5064%     
================================================
  Files          1605       1752       +147     
  Lines        445003     549892    +104889     
================================================
+ Hits         326713     395437     +68724     
- Misses        98242     132309     +34067     
- Partials      20048      22146      +2098     

Flag	Coverage Δ
integration	50.4370% <5.3333%> (?)
unit	73.4575% <58.6666%> (+0.9495%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	26.0836% <ø> (-19.9474%)	⬇️

[wjhuang2016]

/retest

[wjhuang2016]

/retest

[ti-chi-bot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tangenta]

The returning bool value is not used?

[wjhuang2016]

I will check it

[wjhuang2016]

/retest

[Benjamin2037]

LGTM

[wjhuang2016]

/retest

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-09-25 11:16:17.272247453 +0000 UTC m=+1651047.012671393: ☑️ agreed by Benjamin2037.
• 2024-09-25 15:15:12.158447162 +0000 UTC m=+1665381.898871098: ☑️ agreed by tangenta.

[yudongusa]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, tangenta, yudongusa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/owner/OWNERS [Benjamin2037,tangenta]
• pkg/session/OWNERS [yudongusa]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

@wjhuang2016: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-br-integration-test	5471b05	link	true	/test pull-br-integration-test
pull-lightning-integration-test	5471b05	link	true	/test pull-lightning-integration-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[wjhuang2016]

/retest