Skip to content

False positive configuration check when both shard-mode and TLS configuration are configured #11842

@sunxiaoguang

Description

@sunxiaoguang

What did you do?

When task configuration contains both shard-mode and TLS configuration, start task fails

name: "test"
task-mode: all
shard-mode: "pessimistic"
meta-schema: "dm_meta"
ignore-checking-items: ["AUTO_INCREMENT_ID"]

target-database:
  host: "192.168.0.1"
  port: 4000
  user: "root"
  password: "password"

  security:
    ssl-ca: "/path/to/ca.pem"
    ssl-cert: "/path/to/dm.pem"
    ssl-key: "/path/to/dm.key"

What did you expect to see?

Task can start successfully

What did you see instead?

Image

Versions of the cluster

DM version (run dmctl -V or dm-worker -V or dm-master -V):

Git Commit Hash: 45388394a9b50411b1e15c91e65e476d8aafa928
Git Branch: master
UTC Build Time: 2024-12-06 15:24:40
Go Version: go1.23.2
Failpoint Build: false

Upstream MySQL/MariaDB server version:

Downstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

+-----------------------------------------------------------+
| tidb_version()                                            |
+-----------------------------------------------------------+
| Release Version: v7.1.3-serverless                        |
| Edition: Community                                        |
| Git Commit Hash: 2e8be50b073c26b8979c6988a3888ce57b5cec99 |
| Git Branch: release-7.1-serverless                        |
| UTC Build Time: 2024-11-22 15:30:05                       |
| GoVersion: go1.21.11                                      |
| Race Enabled: false                                       |
| TiKV Min Version: 6.1.0                                   |
| Check Table Before Drop: false                            |
| Store: tikv                                               |
+-----------------------------------------------------------+

How did you deploy DM: tiup or manually?

TiUP

Other interesting information (system version, hardware config, etc):

>
>

current status of DM cluster (execute query-status <task-name> in dmctl)

Metadata

Metadata

Assignees

No one assigned

    Labels

    affects-5.4This bug affects the 5.4.x(LTS) versions.affects-6.1This bug affects the 6.1.x(LTS) versions.affects-6.5This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.affects-8.5This bug affects the 8.5.x(LTS) versions.area/dmIssues or PRs related to DM.severity/majortype/bugThe issue is confirmed as a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions