In rare scenarios，mysql enabled gtid mode but replication-manager bootstrapped with no gtid mode

[ProGengi]

The replication-manager is running in K8S and version is V2.3.46.
The image is compiled from source code, and we have modified the startup command to launch replication-manager in the background.
The bootstrap command is：
replication-manager-cli bootstrap --cluster=xxxxx

MySQL enabled gitd_mode and enforce_gtid_consistency

In our testing (approximately ten runs or more), the problem appeared once or twice.

Abnormal log：

time="2025-06-04 22:38:10" level=warning msg="Cluster [dol-mysql] topology (unknown) is not same with target topology (master-slave)." channel=StdOut cluster=dol-mysql code=ERR00092 status=OPENED type=state
time="2025-06-04 22:38:20" level=error msg="Refresh failed in Cleanup on server dol-mysql-0.dol-mysql-peer:3306 Connection is nil, server unreachable" cluster=dol-mysql module=orchestrator type=log
time="2025-06-04 22:38:20" level=error msg="Cleanup error Connection is nil, server unreachable" cluster=dol-mysql module=orchestrator type=log
time="2025-06-04 22:38:20" level=info msg="Assigning a global connection on server dol-mysql-2.dol-mysql-peer:3306" cluster=dol-mysql module=general type=log
time="2025-06-04 22:38:20" level=info msg="Assigning a global connection on server dol-mysql-0.dol-mysql-peer:3306" cluster=dol-mysql module=general type=log
time="2025-06-04 22:38:20" level=info msg="Assigning a global connection on server dol-mysql-1.dol-mysql-peer:3306" cluster=dol-mysql module=general type=log
time="2025-06-04 22:38:20" level=info msg="Replication bootstrapped with old replication style and dol-mysql-0.dol-mysql-peer:3306 as master" cluster=dol-mysql module=general type=log
time="2025-06-04 22:38:20" level=error msg="Replication can't be bootstrap for server dol-mysql-1.dol-mysql-peer:3306 with dol-mysql-0.dol-mysql-peer:3306 as master: Change MASTER statement CHANGE MASTER TO MASTER_host='dol-mysql-0.dol-mysql-peer', MASTER_port=3306, MASTER_user='replicator', MASTER_password='XXX', MASTER_connect_retry=5, MASTER_heartbeat_period=3, MASTER_log_file='', MASTER_log_pos= failed, reason: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 " cluster=dol-mysql
time="2025-06-04 22:38:20" level=info msg="Replication bootstrapped with old replication style and dol-mysql-0.dol-mysql-peer:3306 as master" cluster=dol-mysql module=general type=log
time="2025-06-04 22:38:20" level=error msg="Replication can't be bootstrap for server dol-mysql-2.dol-mysql-peer:3306 with dol-mysql-0.dol-mysql-peer:3306 as master: Change MASTER statement CHANGE MASTER TO MASTER_host='dol-mysql-0.dol-mysql-peer', MASTER_port=3306, MASTER_user='replicator', MASTER_password='XXX', MASTER_connect_retry=5, MASTER_heartbeat_period=3, MASTER_log_file='', MASTER_log_pos= failed, reason: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 " cluster=dol-mysql

Normal logs：

time="2025-06-11 19:35:32" level=info msg="Assigning a global connection on server dol-mysql-2.dol-mysql-peer:3306" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:46" level=info msg="Created metadata for binary logs on dol-mysql-2.dol-mysql-peer:3306" cluster=dol-mysql module=job type=log
time="2025-06-11 19:35:48" level=warning msg="Cluster [dol-mysql] topology (unknown) is not same with target topology (master-slave)." channel=StdOut cluster=dol-mysql code=ERR00092 status=OPENED type=state
time="2025-06-11 19:35:58" level=info msg="Assigning a global connection on server dol-mysql-0.dol-mysql-peer:3306" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:58" level=info msg="Assigning a global connection on server dol-mysql-1.dol-mysql-peer:3306" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:59" level=info msg="Created metadata for binary logs on dol-mysql-0.dol-mysql-peer:3306" cluster=dol-mysql module=job type=log
time="2025-06-11 19:35:59" level=info msg="Created metadata for binary logs on dol-mysql-1.dol-mysql-peer:3306" cluster=dol-mysql module=job type=log
time="2025-06-11 19:35:59" level=info msg="Updated metadata for binary logs on dol-mysql-0.dol-mysql-peer:3306" cluster=dol-mysql module=job type=log
time="2025-06-11 19:35:59" level=info msg="Updated metadata for binary logs on dol-mysql-1.dol-mysql-peer:3306" cluster=dol-mysql module=job type=log
time="2025-06-11 19:35:59" level=info msg="Updated metadata for binary logs on dol-mysql-2.dol-mysql-peer:3306" cluster=dol-mysql module=job type=log
time="2025-06-11 19:35:59" level=info msg="Replication bootstrapped with MySQL GTID replication style and dol-mysql-0.dol-mysql-peer:3306 as master" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:59" level=info msg="Replication bootstrapped with MySQL GTID replication style and dol-mysql-0.dol-mysql-peer:3306 as master" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:59" level=info msg="Server dol-mysql-2.dol-mysql-peer:3306 state transition from Suspect changed to: Slave" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:59" level=info msg="Server dol-mysql-2.dol-mysql-peer:3306 previous state set to: Slave" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:59" level=info msg="Server dol-mysql-1.dol-mysql-peer:3306 state transition from Suspect changed to: Slave" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:59" level=info msg="Server dol-mysql-1.dol-mysql-peer:3306 previous state set to: Slave" cluster=dol-mysql module=general type=log
time="2025-06-11 19:35:59" level=info msg="Server dol-mysql-0.dol-mysql-peer:3306 state transition from Suspect changed to: Master" cluster=dol-mysql module=general type=log
time="2025-06-11 19:36:08" level=info msg="Server dol-mysql-0.dol-mysql-peer:3306 previous state set to: Master" cluster=dol-mysql module=general type=log
time="2025-06-11 19:36:08" level=warning msg="Cluster [dol-mysql] topology (unknown) is not same with target topology (master-slave)." channel=StdOut cluster=dol-mysql code=ERR00092 status=RESOLV type=state

[svaroqui]

Thanks for reporting looking at the code we do a test on ForceSlaveGtid variable you can try to set this true in repman config? Without it i guess it's a matter of timeout for the monitoring to detect the servers are GTID compatible

[ProGengi]

I turned on the ForceSlaveGtid force-slave-gtid-mode = true, however the error still occurred.
Are there any other parameters that also need to be enabled?

[svaroqui]

I would advise that you use 3.1 last release your looks super old

[ProGengi]

thank you. I'll give it a try.