[MXS-2973] Passwords are not updated by maxctrl cluster sync Created: 2020-04-23  Updated: 2021-06-03  Resolved: 2021-06-03

Status: Closed
Project: MariaDB MaxScale
Component/s: maxctrl
Affects Version/s: 2.4.7
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Wagner Bianchi (Inactive) Assignee: markus makela
Resolution: Won't Do Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-3560 MaxScale Cluster Configuration Sync Closed

 Description   

When executing a cluster sync, the passwords are not updated as is described in MXS-2948.

Original description:


Folks,

Setting up two MaxScale instances to be available in an active-passive with keepalived, I use to set up the first one with a basic configuration file and then, use dynamic commands to create the monitor, servers, the service and the listener.

After that, I copy the maxscale.cnf and the .secrets to the other server and, using the maxctrl cluster sync command, I sync all configurations and get the second instance up and running quickly.

root@max01: ~ # maxctrl --hosts 192.168.102.228:8989 cluster sync 192.168.102.227:8989
OK,OK,OK,OK,OK,OK

The case is that, I executed the above steps and got the password variable on the second host as ******, as you can see below, for the monitor definition:

root@max02: maxscale.cnf.d # cat cluster-monitor.cnf
[cluster-monitor]
type=monitor
module=mariadbmon
user=maxmon
password=*****
[...snip...]
replication_user=mariadb
replication_password=*****
[...snip...]
replication_master_ssl=false
assume_unique_hostnames=true
enforce_simple_topology=false

With that, I had an issue when MaxScale wasn't able to connect to backends to pull states:

root@max02: maxscale # maxctrl list servers
┌─────────────┬─────────────────┬──────┬─────────────┬──────────────────┬──────┐
│ Server      │ Address         │ Port │ Connections │ State            │ GTID │
├─────────────┼─────────────────┼──────┼─────────────┼──────────────────┼──────┤
│ server20 │ 192.168.102.23033060           │ Auth Error, Down │      │
├─────────────┼─────────────────┼──────┼─────────────┼──────────────────┼──────┤
│ server21 │ 192.168.102.23133060           │ Auth Error, Down │      │
└─────────────┴─────────────────┴──────┴─────────────┴──────────────────┴──────┘

Can you take a look? Thanks!



 Comments   
Comment by markus makela [ 2020-04-24 ]

This was mentioned in MXS-2948 as well as in the output of --help cluster sync:

 Note: New objects created by `cluster sync` will have a placeholder value and must be manually updated. Passwords for existing objects will not be updated by `cluster sync` and must also be manually updated.

Comment by markus makela [ 2021-06-03 ]

The feature in MXS-2808 will supersede this one.

Generated at Thu Feb 08 04:18:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.