Project

General

Profile

Actions

coordination #64051

closed

[qe-core][functional][epic] Change mysql tests to mariadb integration tests and expand the coverage

Added by mgriessmeier about 4 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
New test
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

Description

giving the story around the mariadb bug recently, we discovered that we lack in having mariadb integration tests.
so let's have this ticket as tracker issue and maybe ask krystina about what makes sense

related resources

Acceptance criteria

  • AC1: mysql test modules are renamed to "mariadb" and mariadb tests are scheduled in the products where mariadb is shipping
  • AC2: mysql references are renamed to mariadb where applicable
  • AC3: New tasks extending the test module are added (see comment#8 and comment#14) and implemented

Subtasks 1 (0 open1 closed)

action #92215: [qe-core] Change mysql tests to mariadb integration testsResolveddheidler

Actions

Related issues 1 (0 open1 closed)

Related to openQA Tests - action #63871: [functional][u] test fails in php7_mysql - no answer from test_mysql_connector.phpResolvedszarate2020-02-26

Actions
Actions #1

Updated by okurz about 4 years ago

Do you think this ticket needs to be regarded with "High" prio though? The issue I have seen and reported in https://bugzilla.suse.com/show_bug.cgi?id=1165151#c15 is that we already have good integration tests but the post_fail_hook is not providing specific log files. "More tests!" isn't always the best solution ;)

Just keep in mind that we already have multiple test modules with "mysql" in name where for recent versions of SLE/openSUSE "mysql" is a backward-compatible alias for "mariadb":

$ git ls-files | grep mysql
data/console/test_mysql_connector.php
tests/console/mysql_odbc.pm
tests/console/mysql_srv.pm
tests/console/php7_mysql.pm

Maybe it's about time to rename these test modules and change to install mariadb directly instead of mysql.

Actions #2

Updated by okurz almost 4 years ago

  • Status changed from New to Rejected
  • Assignee set to okurz

Also there is a mariadb test module already, it's just not used -> #44582

Actions #3

Updated by mgriessmeier almost 4 years ago

yeah, sorry I was way too fast with this, didn't check anything before. thanks for closing

Actions #4

Updated by szarate almost 4 years ago

  • Description updated (diff)
  • Status changed from Rejected to Workable
  • Assignee deleted (okurz)
  • Priority changed from High to Normal
Actions #5

Updated by szarate almost 4 years ago

  • Description updated (diff)
Actions #6

Updated by szarate almost 4 years ago

  • Related to action #63871: [functional][u] test fails in php7_mysql - no answer from test_mysql_connector.php added
Actions #7

Updated by szarate almost 4 years ago

  • Assignee set to szarate
Actions #8

Updated by szarate almost 4 years ago

Mariadb can take a long time when plugins are enabled (rocksdb)

(493/606) Installing: mariadb-10.4.12-3.2.x86_64 .................................................................................................................[done]                                                                     
Additional rpm output:                                                                                                                                                                                                                       
usermod: no changes                                                                                                                                                                                                                          
Job for mariadb.service failed because a timeout was exceeded.                                                                                                                                                                               
See "systemctl  status mariadb.service" and "journalctl  -xe" for details.

INSTALL SONAME 'ha_rocksdb';

May 14 11:44:30 localhost.localdomain mysql-systemd-helper[5617]: mysql.time_zone_transition_type                    OK
May 14 11:44:30 localhost.localdomain mysql-systemd-helper[5617]: mysql.transaction_registry                         OK
May 14 11:44:30 localhost.localdomain mysql-systemd-helper[5617]: Phase 2/7: Installing used storage engines... Skipped
May 14 11:44:30 localhost.localdomain mysql-systemd-helper[5617]: Phase 3/7: Fixing views
May 14 11:44:30 localhost.localdomain mysql-systemd-helper[5617]: mysql.user                                         OK
May 14 11:44:30 localhost.localdomain mysql-systemd-helper[5617]: Phase 4/7: Running 'mysql_fix_privilege_tables'
May 14 11:49:23 localhost.localdomain systemd[1]: mariadb.service: Start-pre operation timed out. Terminating.
May 14 11:49:23 localhost.localdomain systemd[1]: Failed to start MariaDB database server.
May 14 11:49:23 localhost.localdomain systemd[1]: mariadb.service: Unit entered failed state.
May 14 11:49:23 localhost.localdomain systemd[1]: mariadb.service: Failed with result 'timeout'.

So possibly testing with oqgraph and rocksdb plugins should be also done (including migration)

Actions #9

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [functional][u] Add mariadb integration tests to [qe-core][functional] Add mariadb integration tests
Actions #10

Updated by szarate about 3 years ago

  • Assignee deleted (szarate)
Actions #11

Updated by szarate about 3 years ago

In Mariadb 10.5
The S3 storage engine allows one to archive MariaDB tables in Amazon S3, or any third-party public or private cloud that implements S3 API ( MDEV-22606)

Actions #13

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from [qe-core][functional] Add mariadb integration tests to [qe-core][functional] Change mysql tests to mariadb integration tests
  • Target version changed from Milestone 30 to QE-Core: Ready
  • Start date deleted (2020-03-02)
Actions #14

Updated by szarate almost 3 years ago

We mainly cover Mariadb in two places:

tests/console/mysql_odbc
tests/console/mysql_srv

https://openqa.suse.de/tests/overview?arch=&machine=&modules=mysql_srv&distri=sle&version=15-SP3&build=183.1&groupid=110
https://github.com/os-autoinst/os-autoinst-distri-opensuse/search?p=3&q=console%2F%2Amysql

There's coverage and usage within other modules, including PHP7, I would first target the mariadb stuff directly and then after that's done, improve the coverage of php7 to match the testing done over the CLI

Actions #15

Updated by tjyrinki_suse almost 3 years ago

  • Tracker changed from action to coordination
  • Subject changed from [qe-core][functional] Change mysql tests to mariadb integration tests to [qe-core][functional][epic] Change mysql tests to mariadb integration tests
  • Description updated (diff)
  • Target version deleted (QE-Core: Ready)
Actions #16

Updated by tjyrinki_suse almost 3 years ago

  • Target version set to QE-Core: Ready
Actions #17

Updated by tjyrinki_suse almost 3 years ago

  • Target version deleted (QE-Core: Ready)
Actions #18

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from [qe-core][functional][epic] Change mysql tests to mariadb integration tests to [qe-core][functional][epic] Change mysql tests to mariadb integration tests and expand the coverage
Actions #19

Updated by tjyrinki_suse almost 3 years ago

  • Description updated (diff)
Actions #21

Updated by tjyrinki_suse almost 2 years ago

  • Status changed from Workable to Resolved

Multiple instances now tested. There might be more expansion done but this epic as such was finished.

Actions

Also available in: Atom PDF