Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-27914

Some binlog_encryption tests intermittently failing on ppc64le-ubuntu-2110

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.6, 10.5(EOL), 10.7(EOL), 10.8(EOL), 10.9(EOL)
    • N/A
    • Replication, Tests
    • None

    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.

      Attachments

        Issue Links

          Activity

            People

              angelique.sklavounos Angelique Sklavounos (Inactive)
              angelique.sklavounos Angelique Sklavounos (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.