[MDEV-26279] Should be able to configure MASTER_SSL_VERIFY_SERVER_CERT value Created: 2021-07-30  Updated: 2023-03-21  Resolved: 2022-02-25

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Maria M Pflaum Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None


 Description   

It would be good to have the MASTER_SSL_VERIFY_SERVER_CERT be configurable so that when Maxscale calls CHANGE MASTER TO the value will be picked up and used as an option.

This has been unsuccessful in MariaDB 10.3.28-1:
STOP SLAVE;
CHANGE MASTER TO MASTER_HOST='127.0.0.1', MASTER_PORT=3306, MASTER_SSL_VERIFY_SERVER_CERT=1;
START SLAVE;

STOP SLAVE;
CHANGE MASTER TO MASTER_HOST='mydb.myhost.com';
START SLAVE;

 Comments   
Comment by Andrei Elkin [ 2021-11-16 ]

mpflaum, salute!

The 2nd CM wipes off MASTER_SSL_VERIFY_SERVER_CERT value of the 1st CM as well as any other parameters of the 1st CM.
There's no inheritance (if that what was expected). The 2nd CM resets all the parameters to install its own
from the parameter list and the default value rules.

I hope this clarifies.

Cheers,

Andrei

Comment by Maria M Pflaum [ 2022-01-31 ]

ralf.gebhardt@mariadb.com I need to retest this and will get back to you.

Generated at Thu Feb 08 09:44:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.