Bug 1713365
| Summary: | mysqldump unit test fail | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Anna Khaitovich <akhaitov> |
| Component: | mariadb | Assignee: | Michal Schorm <mschorm> |
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Zachar <lzachar> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.7 | CC: | agk, akkaran046, databases-maint, hhorak, mmuzila |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-29 20:41:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1834835 | ||
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: mariadb security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4026 |
Description of problem: mysqldump test fail Version-Release number of selected component (if applicable): mariadb-5.5.60-1.el7_5.x86_64 How reproducible: Always Steps to Reproduce: 1. Install mariadb 2. systemctl start mariadb 3. pushd /usr/share/mysql-test/ 4. su mysql -c './mysql-test-run --force mysqldump 2>&1 Actual results: Logging: ./mysql-test-run --force mysqldump vardir: /usr/share/mysql-test/var Removing old var directory... Creating var directory '/usr/share/mysql-test/var'... Checking supported features... Can't exec "patch": No such file or directory at ./mysql-test-run line 1962. MariaDB Version 5.5.60-MariaDB Installing system database... - SSL connections supported Collecting tests... ============================================================================== TEST RESULT TIME (ms) or COMMENT -------------------------------------------------------------------------- worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019 main.mysqldump [ fail ] Test ended at 2019-05-23 09:25:55 CURRENT_TEST: main.mysqldump mysqldump: Couldn't find table: "non_existing" mysqldump: Got error: 1356: "View 'test.v1' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them" when using LOCK TABLES mysqldump: Couldn't execute 'SHOW FIELDS FROM `v1`': View 'test.v1' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them (1356) mysqldump: Got error: 1083: "Field separator argument is not what is expected; check the manual" when executing 'SELECT INTO OUTFILE' mysqldump: Got error: 1083: "Field separator argument is not what is expected; check the manual" when executing 'SELECT INTO OUTFILE' mysqldump: Got error: 1083: "Field separator argument is not what is expected; check the manual" when executing 'SELECT INTO OUTFILE' mysqldump: user2 has insufficent privileges to SHOW CREATE PROCEDURE `sp1`! mysqldump: Got error: 1146: "Table 'test.???????????????????????' doesn't exist" when using LOCK TABLES /usr/bin/mysqlimport: Error: 1146, Table 'test.words' doesn't exist, when using table: words Error in my_thread_global_end(): 2 threads didn't exit mysqldump: Got error: 1083: "Field separator argument is not what is expected; check the manual" when executing 'SELECT INTO OUTFILE' mysqldump: Got error: 1083: "Field separator argument is not what is expected; check the manual" when executing 'SELECT INTO OUTFILE' mysqldump: user1 has insufficent privileges to SHOW CREATE FUNCTION `hello1`! mysqldump: Got error: 2005: "Unknown MySQL server host 'unknownhost' (2)" when trying to connect mysqldump: Couldn't execute 'SHOW SLAVE STATUS': MySQL server has gone away (2006) --- /usr/share/mysql-test/r/mysqldump.result 2018-04-20 03:16:52.000000000 -0400 +++ /usr/share/mysql-test/r/mysqldump.reject 2019-05-23 09:25:55.302921700 -0400 @@ -4318,11 +4318,12 @@ Event sql_mode time_zone Create Event character_set_client collation_connection Database Collation ee1 UTC CREATE DEFINER=`root`@`localhost` EVENT `ee1` ON SCHEDULE AT '2035-12-31 20:01:23' ON COMPLETION NOT PRESERVE ENABLE DO set @a=5 latin1 latin1_swedish_ci latin1_swedish_ci create event ee2 on schedule at '2018-12-31 21:01:23' do set @a=5; +Warnings: +Note 1588 Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation. create event ee3 on schedule at '2030-12-31 22:01:23' do set @a=5; show events; Db Name Definer Time zone Type Execute at Interval value Interval field Starts Ends Status Originator character_set_client collation_connection Database Collation second ee1 root@localhost UTC ONE TIME 2035-12-31 20:01:23 NULL NULL NULL NULL ENABLED 1 latin1 latin1_swedish_ci latin1_swedish_ci -second ee2 root@localhost UTC ONE TIME 2018-12-31 21:01:23 NULL NULL NULL NULL ENABLED 1 latin1 latin1_swedish_ci latin1_swedish_ci second ee3 root@localhost UTC ONE TIME 2030-12-31 22:01:23 NULL NULL NULL NULL ENABLED 1 latin1 latin1_swedish_ci latin1_swedish_ci drop database second; create database third; @@ -4330,7 +4331,6 @@ show events; Db Name Definer Time zone Type Execute at Interval value Interval field Starts Ends Status Originator character_set_client collation_connection Database Collation third ee1 root@localhost UTC ONE TIME 2035-12-31 20:01:23 NULL NULL NULL NULL ENABLED 1 latin1 latin1_swedish_ci latin1_swedish_ci -third ee2 root@localhost UTC ONE TIME 2018-12-31 21:01:23 NULL NULL NULL NULL ENABLED 1 latin1 latin1_swedish_ci latin1_swedish_ci third ee3 root@localhost UTC ONE TIME 2030-12-31 22:01:23 NULL NULL NULL NULL ENABLED 1 latin1 latin1_swedish_ci latin1_swedish_ci drop database third; set time_zone = 'SYSTEM'; mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/log/main.mysqldump/' to '/usr/share/mysql-test/var/log/main.mysqldump/' -------------------------------------------------------------------------- The servers were restarted 0 times Spent 0.000 of 8 seconds executing testcases Completed: Failed 1/1 tests, 0.00% were successful. Failing test(s): main.mysqldump Expected results: The test passes Additional info: