2022-05-03 22:04:39 io INFO [7f91c2e53e00] starting 8 io-threads, using backend 'linux_epoll'
2022-05-03 22:04:39 main ERROR [7f91c2e53e00] Error: option 'DEFAULT.name' is not supported
When I try to generate the bootstrap files that the mysqlrouter creates we can find that the `name` key is added by it and it's not added by the charm, see below:
root@juju-b70e35-0-lxd-6:/var/lib/mysql/vault-mysql-router# /usr/bin/mysqlrouter --user mysql --name keystone-mysql-router --bootstrap mysqlrouteruser:3f4m6w6r2HFjGkfXnbHP3Mr6mphcpxys@10.246.114.60 --direc
tory /var/lib/mysql/keystone-mysql-router --conf-use-sockets --conf-bind-address 127.0.0.1 --conf-base-port 3306 --disable-rest --force
# Bootstrapping MySQL Router instance at '/var/lib/mysql/keystone-mysql-router'...
- Creating account(s) (only those that are needed, if any)
- Verifying account (using it to run SQL queries that would be run by Router)
- Storing account in keyring
- Adjusting permissions of generated files
- Creating configuration /var/lib/mysql/keystone-mysql-router/mysqlrouter.conf
# MySQL Router 'keystone-mysql-router' configured for the InnoDB Cluster 'jujuCluster'
After this MySQL Router has been started with the generated configuration
root@juju-b70e35-0-lxd-6:/var/lib/mysql/vault-mysql-router# less /var/lib/mysql/keystone-mysql-router/mysqlrouter.conf
root@juju-b70e35-0-lxd-6:/var/lib/mysql/vault-mysql-router# grep -B1 name /var/lib/mysql/keystone-mysql-router/mysqlrouter.conf
[DEFAULT]
name=keystone-mysql-router
I'm seeing this error:
2022-05-03 22:04:39 io INFO [7f91c2e53e00] starting 8 io-threads, using backend 'linux_epoll'
2022-05-03 22:04:39 main ERROR [7f91c2e53e00] Error: option 'DEFAULT.name' is not supported
The error can be reproduced using this bundle http:// paste.ubuntu. com/p/mdY9dJhkt H/ + the patch recently merged at https:/ /review. opendev. org/c/openstack /charm- mysql-router/ +/834359 (probably at this point in time the change should be available in the latest/edge channel).
When I try to generate the bootstrap files that the mysqlrouter creates we can find that the `name` key is added by it and it's not added by the charm, see below:
root@juju- b70e35- 0-lxd-6: /var/lib/ mysql/vault- mysql-router# /usr/bin/ mysqlrouter --user mysql --name keystone- mysql-router --bootstrap mysqlrouteruser :3f4m6w6r2HFjGk fXnbHP3Mr6mphcp xys@10. 246.114. 60 --direc mysql/keystone- mysql-router --conf-use-sockets --conf-bind-address 127.0.0.1 --conf-base-port 3306 --disable-rest --force mysql/keystone- mysql-router' ...
tory /var/lib/
# Bootstrapping MySQL Router instance at '/var/lib/
- Creating account(s) (only those that are needed, if any) mysql/keystone- mysql-router/ mysqlrouter. conf
- Verifying account (using it to run SQL queries that would be run by Router)
- Storing account in keyring
- Adjusting permissions of generated files
- Creating configuration /var/lib/
# MySQL Router 'keystone- mysql-router' configured for the InnoDB Cluster 'jujuCluster'
After this MySQL Router has been started with the generated configuration
$ /usr/bin/ mysqlrouter -c /var/lib/ mysql/keystone- mysql-router/ mysqlrouter. conf
InnoDB Cluster 'jujuCluster' can be reached by connecting to:
## MySQL Classic protocol
- Read/Write Connections: localhost:3306, /var/lib/ mysql/keystone- mysql-router/ mysql.sock mysql/keystone- mysql-router/ mysqlro. sock
- Read/Only Connections: localhost:3307, /var/lib/
## MySQL X protocol
- Read/Write Connections: localhost:3308, /var/lib/ mysql/keystone- mysql-router/ mysqlx. sock mysql/keystone- mysql-router/ mysqlxro. sock
- Read/Only Connections: localhost:3309, /var/lib/
root@juju- b70e35- 0-lxd-6: /var/lib/ mysql/vault- mysql-router# less /var/lib/ mysql/keystone- mysql-router/ mysqlrouter. conf b70e35- 0-lxd-6: /var/lib/ mysql/vault- mysql-router# grep -B1 name /var/lib/ mysql/keystone- mysql-router/ mysqlrouter. conf mysql-router
root@juju-
[DEFAULT]
name=keystone-