Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL)
-
None
Description
encryption.innodb-log-encrypt 'xtradb' [ skipped ] Test requires InnoDB.
|
***Warnings generated in error logs during shutdown after running tests: encryption.innodb-log-encrypt
|
|
|
2015-11-02 16:33:37 140648474441568 [ERROR] /data/repo/git/10.1-bug/sql/mysqld: Error while setting value 'aes_ctr' to 'file-key-management-encryption-algorithm'
|
2015-11-02 16:33:37 140648474441568 [ERROR] Parsing options for plugin 'file_key_management' failed.
|
2015-11-02 16:33:37 140648474441568 [ERROR] InnoDB: cannot enable encryption, encryption plugin is not available
|
2015-11-02 16:33:37 140648474441568 [ERROR] Plugin 'InnoDB' init function returned error.
|
2015-11-02 16:33:37 140648474441568 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
|
It happens, for example, in buildbot on bld-dan-debug which builds with the bundled SSL.
The failure itself can be expected, since AES_CTR is not supported, but it's unclear what to do with the test.
- adding include/have_openssl.inc does not help, because it's a runtime check, the errors will be generated anyway;
- adding --loose to InnoDB options does not help, because the options themselves are valid;
- adding a local suppression does not help, because the warnings are considered as being generated on shutdown (see
MDEV-781); - adding global suppressions seems to be too radical.
Attachments
Activity
commit 6189951003fd4ce1c925516b3b77475a2eb14889
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Tue Nov 3 16:03:25 2015 +0200
MDEV-9063: encryption.innodb-log-encrypt produces warnings in error logs on builds with bundled SSL
Test used aes_ctr that is not available everywhere when aes_cbc is fine also
for this test.
Increasing the priority – it turns out we have many builders that have the same problem.