Bug #119941 MySQL Router is not started when cluster created with initDB.clone feature
Submitted: 25 Feb 14:35 Modified: 26 Feb 9:20
Reporter: Tamas Kelemen Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Operator Severity:S3 (Non-critical)
Version:8.0.35-2.0.12 OS:Any
Assigned to: CPU Architecture:Any

[25 Feb 14:35] Tamas Kelemen 
Description:
When cloning data from another cluster, group replication is working great:

NAME         STATUS   ONLINE   INSTANCES   ROUTERS   AGE
mysql-test   ONLINE   3        3           1         21m

NAME                    READY   AGE
mysql-test              3/3     22m

Router deployment is not scaled up from 0 instances.

And also it seems that router user is not created in the cluster:
mysql-test-router-7464d4dbb5-fz92q router [Entrypoint] MYSQL_CREATE_ROUTER_USER is 0, Router will reuse mysqlrouter account at runtime
mysql-test-router-7464d4dbb5-fz92q router [Entrypoint] Succesfully contacted mysql server at mysql-test-instances.kiskele.svc.cluster.local:3306. Checking for cluster state.
mysql-test-router-7464d4dbb5-fz92q router [Entrypoint] ERROR: Can not connect to database. Exiting.
mysql-test-1 mysql 2026-02-25T14:32:13.747552Z 125 [Note] [MY-010926] [Server] Access denied for user 'mysqlrouter'@'10.42.10.153' (using password: YES)

How to repeat:
Create cluster with parameters:

apiVersion: mysql.oracle.com/v2
kind: InnoDBCluster
metadata:
  name: mysql-test
spec:
  instances: 3
  initDB:
    clone:
      donorUrl: root@mysql.kiskele.svc.cluster.local:3306
      secretKeyRef:
        name: mysql-secret
  router:
    instances: 1
[26 Feb 9:20] Tamas Kelemen 
Seems to be fixed in latest version: 9.6.0-2.2.7