[MDEV-30293] mariabackup fail with --galera-info option with Non-Galera cluster MariaDB servers Created: 2022-12-23  Updated: 2022-12-29  Resolved: 2022-12-29

Status: Closed
Project: MariaDB Server
Component/s: Backup
Affects Version/s: 10.3, 10.4, 10.5, 10.6, 10.7
Fix Version/s: 10.11.2, 10.3.38, 10.4.28, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5

Type: Bug Priority: Major
Reporter: Pramod Mahto Assignee: Julius Goryavsky
Resolution: Fixed Votes: 0
Labels: None


 Description   

User with appropriate privileges failed to backup non-galera MariaDB server while using option --galera-info.

KB says :- https://mariadb.com/kb/en/mariabackup-options/#-galera-info If the server is not a Galera Cluster node, then this option has no effect. But it does affect mariabackup , backup keeps failing for all CS.

*Test case :- *

Server version: 10.3.30-MariaDB MariaDB Server
Server version: 10.4.19-MariaDB MariaDB Server
Server version: 10.5.18-MariaDB MariaDB Server
Server version: 10.6.11-MariaDB MariaDB Server
Server version: 10.7.7-MariaDB MariaDB Server

 
[root@mariadb_stand backup]# mariabackup -u root --galera-info  --backup --target_dir=/tmp/backup/ > /tmp/backup/output.log 2>&1
 
[root@mariadb_stand backup]# tail -3 output.log
[00] 2022-12-21 13:25:12 Failed to get master wsrep state from SHOW STATUS.
mariabackup: Stopping log copying thread.[00] 2022-12-21 13:25:12 >> log scanned up to (1626148)
 
[root@mariadb_stand backup]# mariabackup -u mariabackup -pMaria@128807 --backup --galera-info --target_dir=/tmp/backup/ > /tmp/backup/output.log 2>&1
 
[root@mariadb_stand backup]# tail -3 output.log
[00] 2022-12-21 13:25:29 Failed to get master wsrep state from SHOW STATUS.
mariabackup: Stopping log copying thread.[00] 2022-12-21 13:25:29 >> log scanned up to (1626364)



 Comments   
Comment by Jan Lindström (Inactive) [ 2022-12-28 ]

ok to push.

Comment by Julius Goryavsky [ 2022-12-29 ]

Fixed, https://github.com/MariaDB/server/commit/6710fe4b42a0909072ff8b9fb243e73bcf740ffb

Generated at Thu Feb 08 10:15:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.