Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.1.4
-
None
Description
Effect file_key_management_plugin where first tables with key_id 1-4 are created, then key_id is changed in all tables to 5. Restart server with different key file where keys 1-4 are deleted and new key_id 6-9 are introduced but naturally key 5 remains the same. Idea is to alter tables back to use changed keys for key_ids 6-9.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | innodb_page_encryption_key_change.test [ 38217 ] |
150527 12:10:56 [ERROR] InnoDB: Tablespace id 9 encrypted but encryption service not available. Can't continue opening tablespace.
|
|
|
2015-05-27 12:10:56 7f69cdbbe780 InnoDB: Assertion failure in thread 140092399937408 in file ha_innodb.cc line 21135
|
Problem is that key_id 1 can't be removed.
| Description | Effect file_key_management_plugin where first tables with key_id 1-4 are created, then key_id is changed in all tables to 5. Restart server with different key file where keys 1-4 are changed but naturally key 5 remains the same. Idea is to alter tables back to use changed keys for key_ids 1-4. | Effect file_key_management_plugin where first tables with key_id 1-4 are created, then key_id is changed in all tables to 5. Restart server with different key file where keys 1-4 are deleted and new key_id 6-9 are introduced but naturally key 5 remains the same. Idea is to alter tables back to use changed keys for key_ids 6-9. |
| Summary | nnoDB: Assertion failure in file ha_innodb.cc line 21135 when changing key_id | Tables with encryption=yes using file_key_management plugin are not encrypted |
| Priority | Critical [ 2 ] | Blocker [ 1 ] |
| Fix Version/s | 10.1.5 [ 18813 ] | |
| Fix Version/s | 10.1 [ 16100 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
commit a25ccd4f83912e02091abe1cba8515266483559b
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Wed May 27 15:37:13 2015 +0300
MDEV-8238: Tables with encryption=yes using file_key_management plugin are not encrypted
Analysis: Problem was that encryption was skipped.
Fixed by making sure that tables with ENCRYPTED=YES are encrypted.
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 67726 ] | MariaDB v4 [ 149216 ] |
Actual keys can be changed as long the key_id does not change.