dm: fix integration test in rocky8.9

[River2000i]

What problem does this PR solve?

Issue Number: close #11752

What is changed and how it works?

Check List

Tests

• Integration test
  https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_dm_integration_test/detail/pull_dm_integration_test/3401/pipeline/

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

[ti-chi-bot]

Hi @River2000i. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[purelind]

/ok-to-test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.1656%. Comparing base (b2a4f9a) to head (3966225).
Report is 4 commits behind head on master.

Additional details and impacted files

Components	Coverage Δ
cdc	59.6051% <ø> (+0.0295%)	⬆️
dm	50.0461% <ø> (+0.0096%)	⬆️
engine	53.2110% <ø> (-0.0283%)	⬇️

Flag	Coverage Δ
unit	55.1656% <ø> (+0.0145%)	⬆️

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

@@               Coverage Diff                @@
##             master     #11751        +/-   ##
================================================
+ Coverage   55.1510%   55.1656%   +0.0145%     
================================================
  Files          1002       1002                
  Lines        137399     137399                
================================================
+ Hits          75777      75797        +20     
+ Misses        56074      56060        -14     
+ Partials       5548       5542         -6     

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[River2000i]

/retest
not relate fail

"Message": "startLocation: [position: (dm-it-d057503c-049a-4b78-8f1f-52dd03595422-b19zl-29htb-bin.000001, 42228), gtid-set: 013005f3-a328-11ef-a043-827aabe578a7:1-194], endLocation: [position: (dm-it-d057503c-049a-4b78-8f1f-52dd03595422-b19zl-29htb-bin.000001, 42353), gtid-set: 013005f3-a328-11ef-a043-827aabe578a7:1-195], origin SQL: [alter table shardddl1.tb1 add column b int after a]: fail to do etcd txn operation: txn commit failed",

[River2000i]

/retest
not relate fail

• mkdir /home/jenkins/agent/workspace/pingcap/tiflow/pull_dm_integration_test/mysql-ssl
• cp -r /var/lib/mysql/.pem /home/jenkins/agent/workspace/pingcap/tiflow/pull_dm_integration_test/mysql-ssl/
  cp: cannot stat '/var/lib/mysql/.pem': No such file or directory
  script returned exit code 1

[River2000i]

/retest

[purelind]

/test dm-integration-test

[purelind]

/test cdc-integration-kafka-test dm-integration-test

[River2000i]

/retest

[River2000i]

/retest

[purelind]

/retest

[River2000i]

/retest
flaky test

[GMHDBJD]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GMHDBJD, lance6716

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:

• dm/OWNERS [GMHDBJD,lance6716]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-12-02 11:16:46.961088164 +0000 UTC m=+1067194.580742674: ☑️ agreed by lance6716.
• 2024-12-03 03:22:29.645177423 +0000 UTC m=+1125137.264831936: ☑️ agreed by GMHDBJD.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #11924.