[MDEV-29637] binlog_encryption.encrypted_master sometimes fails in BB with ER_PARSE_ERROR (1064) Created: 2022-09-26  Updated: 2022-09-26

Status: Open
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Angelique Sklavounos (Inactive) Assignee: Angelique Sklavounos (Inactive)
Resolution: Unresolved Votes: 0
Labels: None


 Description   

Also happens with binlog_encryption.encrypted_slave. Appears to happen mostly on aarch64 builders recently, but has failed on ppc64le, s390x, and amd64.

10.6 772e3f61e

binlog_encryption.encrypted_master 'ctr,innodb,stmt' w14 [ fail ]
        Test ended at 2022-07-27 06:16:37
 
CURRENT_TEST: binlog_encryption.encrypted_master
mysqltest: In included file "./include/sync_slave_sql_with_io.inc": 
included from /home/buildbot/aarch64-rhel-9/build/mysql-test/suite/binlog_encryption/encrypted_master.test at line 163:
At line 44: query 'if (`SELECT IFNULL($_sync_slave_sql_with_io_errno, -1) < 0`)
{' failed: ER_PARSE_ERROR (1064): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ' -1) < 0' at line 1
 
The result from queries just before the failure was:
< snip >
DROP DATABASE database_name_to_encrypt;
DROP USER new_user_name_to_encrypt;
DROP SERVER server_name_to_encrypt;
#############################
# Final checks for the master
#############################
NOT FOUND /_to_encrypt.*/ in master-bin.0*
NOT FOUND /COMMIT.*/ in master-bin.0*
NOT FOUND /TIMESTAMP.*/ in master-bin.0*
include/save_master_pos.inc
#############################
# Final checks for the slave
#############################
connection server_2;
include/sync_io_with_master.inc
FOUND 1 /_to_encrypt.*/ in slave-relay-bin.0*
FOUND 1 /COMMIT.*/ in slave-relay-bin.0*
FOUND 1 /TIMESTAMP.*/ in slave-relay-bin.0*
include/start_slave.inc
include/sync_slave_sql_with_io.inc


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