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

Add Galera ist and sst tests using mariabackup

Details

    Attachments

      Issue Links

        blocks

        Task - A task that needs to be done. MDEV-15522 Change galera suite MTR tests to use mariabackup instead of xtrabackup

        • Critical - Crashes, loss of data, severe memory leak.
        • Closed
        causes

        Bug - A problem which impairs or prevents the functions of the product. MDEV-18021 Galera test galera_sst_mariabackup_table_options fails if AES_CTR is not available

        • Major - Major loss of function.
        • Closed
        is blocked by

        Task - A task that needs to be done. MDEV-17321 add test galera_sst_mariabackup_encrypt_with_key

        • Major - Major loss of function.
        • Closed

        Task - A task that needs to be done. MDEV-17336 add test galera_ist_mariabackup_innodb_flush_logs to galera test suite

        • Major - Major loss of function.
        • Closed

        Activity

          Ascending order - Click to sort in descending order
          marko Marko Mäkelä added a comment -

          I had to disable a test when merging this to 10.3.

          CURRENT_TEST: galera.galera_sst_mariabackup_table_options
          		 
          …
          		 
          2018-11-26 14:00:15 0 [ERROR] /dev/shm/10.3/sql/mysqld: unknown variable 'file-key-management-encryption-algorithm=aes_ctr'
          		 
          2018-11-26 14:00:15 0 [ERROR] Aborting

          Please fix.

          marko Marko Mäkelä added a comment - I had to disable a test when merging this to 10.3. CURRENT_TEST: galera.galera_sst_mariabackup_table_options … 2018-11-26 14:00:15 0 [ERROR] /dev/shm/10.3/sql/mysqld: unknown variable 'file-key-management-encryption-algorithm=aes_ctr' 2018-11-26 14:00:15 0 [ERROR] Aborting Please fix.
          marko Marko Mäkelä added a comment -

          The reason why the test fails for me in 10.3 or 10.4 is that when I compile with

          cmake -DWITH_SSL=bundled

          then, for some reason, aes_ctr will not be enabled:

          static const char *encryption_algorithm_names[]=
          		 
          {
          		 
            "aes_cbc",
          		 
          #ifdef HAVE_EncryptAes128Ctr
          		 
            "aes_ctr",
          		 
          #endif
          		 
            0
          		 
          };

          In 10.2 with identical build options, it is available.

          Do we really have to test with aes_ctr, or would it suffice to test with aes_cbc which is always available? If aes_ctr is truly needed, then the test should be skipped when it is not available.

          marko Marko Mäkelä added a comment - The reason why the test fails for me in 10.3 or 10.4 is that when I compile with cmake -DWITH_SSL=bundled then, for some reason, aes_ctr will not be enabled: static const char *encryption_algorithm_names[]= { "aes_cbc" , #ifdef HAVE_EncryptAes128Ctr "aes_ctr" , #endif 0 }; In 10.2 with identical build options, it is available. Do we really have to test with aes_ctr , or would it suffice to test with aes_cbc which is always available? If aes_ctr is truly needed, then the test should be skipped when it is not available.
          marko Marko Mäkelä added a comment -

          Actually, the test fails already in 10.1 when aes_ctr is not available.

          marko Marko Mäkelä added a comment - Actually, the test fails already in 10.1 when aes_ctr is not available.
          marko Marko Mäkelä added a comment -

          The problem with aes_ctr was filed as MDEV-18021.

          marko Marko Mäkelä added a comment - The problem with aes_ctr was filed as MDEV-18021 .

          People

            jplindst Jan Lindström (Inactive)
            jplindst Jan Lindström (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.