[MDEV-14427] encryption.innodb-bad-key-change failed in buildbot Created: 2017-11-17  Updated: 2018-02-08  Resolved: 2018-02-08

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.3
Fix Version/s: 10.1.32, 10.2.13, 10.3.5

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos7-amd64/builds/6242/steps/mtr/logs/stdio

encryption.innodb-bad-key-change 'cbc,innodb' w1 [ fail ]
 
        Test ended at 2017-11-17 02:22:23
 
 
 
CURRENT_TEST: encryption.innodb-bad-key-change
 
--- /usr/share/mysql-test/suite/encryption/r/innodb-bad-key-change.result	2017-11-17 00:37:04.000000000 -0500
 
+++ /dev/shm/var/1/log/innodb-bad-key-change.reject	2017-11-17 02:22:22.645266335 -0500
 
@@ -29,7 +29,6 @@
 
 ERROR 42S02: Table 'test.t1' doesn't exist in engine
 
 SHOW WARNINGS;
 
 Level	Code	Message
 
-Warning	192	Table test/t1 in tablespace  is encrypted but encryption service or used key_id is not available.  Can't continue reading table.
 
 Error	1932	Table 'test.t1' doesn't exist in engine
 
 DROP TABLE t1;
 
 Warnings:
 
 
 
mysqltest: Result length mismatch



 Comments   
Comment by Jan Lindström (Inactive) [ 2018-02-08 ]

commit 3969d97e6ac29025a5ae1b425339e075546bc3f9
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Thu Feb 8 14:55:01 2018 +0200

MDEV-14427: encryption.innodb-bad-key-change failed in buildbot

Timing problem as sometimes table is marked as encrypted but
sometimes we are not sure and table is just marked missing.

Comment by Jan Lindström (Inactive) [ 2018-02-08 ]

Merged also to 10.1: commit 06d77eb43a5f1e5bc24555e51d19d209d2b92615
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Thu Feb 8 14:55:01 2018 +0200

MDEV-14427: encryption.innodb-bad-key-change failed in buildbot

Timing problem as sometimes table is marked as encrypted but
sometimes we are not sure and table is just marked missing.

Generated at Thu Feb 08 08:13:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.