[MDEV-27914] Some binlog_encryption tests intermittently failing on ppc64le-ubuntu-2110 Created: 2022-02-22  Updated: 2022-03-14  Resolved: 2022-03-14

Status: Closed
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.5, 10.6, 10.7, 10.8, 10.9
Fix Version/s: N/A

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

Issue Links:
Duplicate
duplicates MDBF-351 buildbot: builder ppc64le-ubuntu-211... Closed

 Description   

There are various failures of binlog_encryption.* tests on ppc64le-ubuntu-2110 with the statement "ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement"


For example, binlog_encryption.encrytped_slave, ctr,innodb,stmt fails are as follows:
10.6 120480d15b764d03d5d36fb68735a1975ceb3454
https://buildbot.mariadb.org/#/builders/337/builds/868/steps/6/logs/stdio

binlog_encryption.encrypted_slave 'ctr,innodb,stmt' w12 [ fail ]
        Test ended at 2022-02-21 23:25:09
 
CURRENT_TEST: binlog_encryption.encrypted_slave
mysqltest: In included file "/home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/testdata.inc": 
included from /home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/encrypted_slave.test at line 39:
At line 169: query 'CALL proc_name_to_encrypt('file_name_to_encrypt',@useless_var_to_encrypt)' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
The result from queries just before the failure was:
< snip >
WHILE counter_name_to_encrypt<12 DO
SELECT COUNT(*) INTO @cnt FROM innodb_table_name_to_encrypt;
INSERT INTO innodb_table_name_to_encrypt 
SELECT int_column_name_to_encrypt+@cnt, NOW(6), blob_column_name_to_encrypt, NULL, NULL
FROM innodb_table_name_to_encrypt
ORDER BY int_column_name_to_encrypt;
SET counter_name_to_encrypt = counter_name_to_encrypt+1;
END WHILE;
COMMIT;
END
$$
INSERT INTO myisam_table_name_to_encrypt
SELECT NULL, 'char_literal_to_encrypt', NULL, 'text_to_encrypt';
INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
CALL proc_name_to_encrypt('file_name_to_encrypt',@useless_var_to_encrypt);

Also seen on:
10.5 b69191bbb2278fce92b470e8e3abafe048166e39
https://buildbot.mariadb.org/#/builders/337/builds/832/steps/6/logs/stdio

10.7 c76bdc57ffb08043e7b509a188d4626d0f3063c9
https://buildbot.mariadb.org/#/builders/337/builds/823/steps/6/logs/stdio

10.8 3b06415cb8dfc2b10d9604950f6ed945bc016425
https://buildbot.mariadb.org/#/builders/337/builds/793/steps/6/logs/stdio

10.9 bbe99cd4e2d7c83a06dd93ea88af97f2d5796810
https://buildbot.mariadb.org/#/builders/337/builds/827/steps/6/logs/stdio

It is the same with ctr,innodb,row; ctr,innodb,mix; cbc,innodb,mix; cbc,innodb,row.

Will put in separate comments the other tests and the queries they fail on. It is not definite they are caused by the same problem, but it is suggested as these fails seem isolated to this test suite and on this test environment.



 Comments   
Comment by Angelique Sklavounos (Inactive) [ 2022-02-22 ]

binlog_encryption.rpl_stm_relay_ign_space (innodb,stmt)

binlog_encryption.rpl_stm_relay_ign_space 'innodb,stmt' w15 [ fail ]
        Test ended at 2022-02-21 23:25:13
 
CURRENT_TEST: binlog_encryption.rpl_stm_relay_ign_space
mysqltest: In included file "./include/diff_tables.inc": 
included from ./suite/rpl/include/rpl_stm_relay_ign_space.inc at line 101:
included from /home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/rpl_stm_relay_ign_space.test at line 2:
At line 170: query 'SELECT * INTO OUTFILE '$_dt_outfile' FROM $_dt_database.$_dt_table ORDER BY `$_dt_column_list`' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
 
The result from queries just before the failure was:
include/master-slave.inc
[connection master]
include/assert.inc [Assert that relay log space is close to the limit]
include/diff_tables.inc [master:test.t1,slave:test.t1]

Comment by Angelique Sklavounos (Inactive) [ 2022-02-22 ]

binlog_encryption.rpl_special_charset (mix, row, stmt)

binlog_encryption.rpl_special_charset 'mix' w8 [ fail ]
        Test ended at 2022-02-21 23:25:08
 
CURRENT_TEST: binlog_encryption.rpl_special_charset
mysqltest: In included file "./include/diff_tables.inc": 
included from ./suite/rpl/include/rpl_special_charset.inc at line 29:
included from /home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/rpl_special_charset.test at line 2:
At line 170: query 'SELECT * INTO OUTFILE '$_dt_outfile' FROM $_dt_database.$_dt_table ORDER BY `$_dt_column_list`' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
 
The result from queries just before the failure was:
include/master-slave.inc
[connection master]
call mtr.add_suppression("'utf16' can not be used as client character set");
CREATE TABLE t1(i VARCHAR(20));
INSERT INTO t1 VALUES (0xFFFF);
connection slave;
include/diff_tables.inc [master:t1, slave:t1]

Comment by Angelique Sklavounos (Inactive) [ 2022-02-22 ]

binlog_encryption.rpl_mixed_binlog_max_cache_size (mix)

binlog_encryption.rpl_mixed_binlog_max_cache_size 'mix' w9 [ fail ]
        Test ended at 2022-02-18 10:16:43
 
CURRENT_TEST: binlog_encryption.rpl_mixed_binlog_max_cache_size
mysqltest: In included file "./include/diff_tables.inc": 
included from ./suite/rpl/include/rpl_binlog_max_cache_size.test at line 92:
included from /home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/rpl_mixed_binlog_max_cache_size.test at line 7:
At line 170: query 'SELECT * INTO OUTFILE '$_dt_outfile' FROM $_dt_database.$_dt_table ORDER BY `$_dt_column_list`' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
 
The result from queries just before the failure was:
< snip >
SET GLOBAL max_binlog_stmt_cache_size = 4096;
SET GLOBAL binlog_stmt_cache_size = 4096;
disconnect master;
connect  master,127.0.0.1,root,,test,$MASTER_MYPORT,;
CREATE TABLE t1(a INT PRIMARY KEY, data VARCHAR(30000)) ENGINE=Innodb;
CREATE TABLE t2(a INT PRIMARY KEY, data VARCHAR(30000)) ENGINE=MyIsam;
CREATE TABLE t3(a INT PRIMARY KEY, data VARCHAR(30000)) ENGINE=Innodb;
########################################################################################
#                                   1 - SINGLE STATEMENT
########################################################################################
connection master;
*** Single statement on transactional table ***
Got one of the listed errors
*** Single statement on non-transactional table ***
Got one of the listed errors
include/wait_for_slave_sql_error_and_skip.inc [errno=1590]
*** Single statement on both transactional and non-transactional tables. ***
Got one of the listed errors
include/wait_for_slave_sql_error_and_skip.inc [errno=1590]
include/diff_tables.inc [master:t1,slave:t1]

Comment by Angelique Sklavounos (Inactive) [ 2022-02-22 ]

binlog_encryption.rpl_loadfile (mix, row)

binlog_encryption.rpl_loadfile 'mix'     w2 [ fail ]
        Test ended at 2022-02-21 23:25:12
 
CURRENT_TEST: binlog_encryption.rpl_loadfile
mysqltest: In included file "./suite/rpl/include/rpl_loadfile.inc": 
included from /home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/rpl_loadfile.test at line 2:
At line 72: query 'SELECT repeat('x',20) INTO OUTFILE '$file'' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
 
The result from queries just before the failure was:
< snip >
abductor
abductors
abducts
Abe
abed
Abel
Abelian
Abelson
Aberdeen
Abernathy
aberrant
aberration
 
connection master;
DROP PROCEDURE IF EXISTS test.p1;
DROP TABLE test.t1;
connection slave;
include/rpl_reset.inc
connection master;
SELECT repeat('x',20) INTO OUTFILE 'MYSQLTEST_VARDIR/tmp/bug_39701.data';

Comment by Angelique Sklavounos (Inactive) [ 2022-02-22 ]

binlog_encryption.rpl_loaddata_local (mix, row)

binlog_encryption.rpl_loaddata_local 'mix' w23 [ fail ]
        Test ended at 2022-02-21 23:25:11
 
CURRENT_TEST: binlog_encryption.rpl_loaddata_local
mysqltest: In included file "./suite/rpl/include/rpl_loaddata_local.inc": 
included from /home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/rpl_loaddata_local.test at line 2:
At line 30: query 'select * into outfile '$MYSQLD_DATADIR/rpl_loaddatalocal.select_outfile' from t1' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
 
The result from queries just before the failure was:
include/master-slave.inc
[connection master]
create table t1(a int);
select * into outfile 'MYSQLD_DATADIR/rpl_loaddatalocal.select_outfile' from t1;

Comment by Angelique Sklavounos (Inactive) [ 2022-02-22 ]

binlog_encryption.encrypted_master (cbc,innodb,mix; cbc,innodb,row; cbc,innodb,stmt; ctr,innodb,mix; ctr,innodb,row; ctr,innodb,statement)

binlog_encryption.encrypted_master 'cbc,innodb,mix' w9 [ fail ]
        Test ended at 2022-02-21 23:25:09
 
CURRENT_TEST: binlog_encryption.encrypted_master
mysqltest: In included file "/home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/testdata.inc": 
included from /home/buildbot/ppc64le-ubuntu-2110/build/mysql-test/suite/binlog_encryption/encrypted_master.test at line 65:
At line 169: query 'CALL proc_name_to_encrypt('file_name_to_encrypt',@useless_var_to_encrypt)' failed: ER_OPTION_PREVENTS_STATEMENT (1290): The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
 
The result from queries just before the failure was:
< snip >
WHILE counter_name_to_encrypt<12 DO
SELECT COUNT(*) INTO @cnt FROM innodb_table_name_to_encrypt;
INSERT INTO innodb_table_name_to_encrypt 
SELECT int_column_name_to_encrypt+@cnt, NOW(6), blob_column_name_to_encrypt, NULL, NULL
FROM innodb_table_name_to_encrypt
ORDER BY int_column_name_to_encrypt;
SET counter_name_to_encrypt = counter_name_to_encrypt+1;
END WHILE;
COMMIT;
END
$$
INSERT INTO myisam_table_name_to_encrypt
SELECT NULL, 'char_literal_to_encrypt', NULL, 'text_to_encrypt';
INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
INSERT INTO myisam_table_name_to_encrypt (char_column_name_to_encrypt) 
SELECT char_column_name_to_encrypt FROM myisam_table_name_to_encrypt;
CALL proc_name_to_encrypt('file_name_to_encrypt',@useless_var_to_encrypt);

Comment by Angelique Sklavounos (Inactive) [ 2022-03-14 ]

Found MDBF-351.

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