| Bug #21331 | Instance Manager: Connect problems in tests | ||
|---|---|---|---|
| Submitted: | 28 Jul 2006 16:06 | Modified: | 31 Aug 2006 18:32 |
| Reporter: | Joerg Bruehe | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Instance Manager | Severity: | S3 (Non-critical) |
| Version: | 5.0.21 and up | OS: | Any (Some Unix (see text)) |
| Assigned to: | Alexander Nozdrin | CPU Architecture: | Any |
[28 Aug 2006 19:07]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/10951 ChangeSet@1.2246, 2006-08-28 23:08:42+04:00, anozdrin@alik. +15 -0 Preliminary patch for the following bugs: - BUG#15934: Instance manager fails to work; - BUG#18020: IM connect problem; - BUG#18027: IM: Server_ID differs; - BUG#18033: IM: Server_ID not reported; - BUG#21331: Instance Manager: Connect problems in tests; The only test suite has been changed (server codebase has not been modified).
[28 Aug 2006 21:21]
Konstantin Osipov
Kent looked at the patch and okayed it (on IRC)
[29 Aug 2006 11:45]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/10998 ChangeSet@1.2247, 2006-08-29 15:46:40+04:00, anozdrin@alik. +16 -0 Preliminary patch for the following bugs: - BUG#15934: Instance manager fails to work; - BUG#18020: IM connect problem; - BUG#18027: IM: Server_ID differs; - BUG#18033: IM: Server_ID not reported; - BUG#21331: Instance Manager: Connect problems in tests; The only test suite has been changed (server codebase has not been modified).
[29 Aug 2006 11:49]
Alexander Nozdrin
Pushed into 5.0-rt tree.
[31 Aug 2006 9:56]
Alexander Nozdrin
Merged into 5.0 tree, currently tagged 5.0.25; merged into 5.1 tree, currently tagged 5.1.12-beta.
[31 Aug 2006 18:32]
Paul DuBois
Test suite change. No changelog entry needed.
Description: This symptom is known since (at least) 5.0.21, but it seems it was not yet reported. Happens on different platforms in different tests - this is from 5.0.24: ===== im_daemon_life_cycle [ fail ] Errors are (from /PATH/mysqltest-time) : mysqltest: In included file "./include/im_check_os.inc": At line 1: Could not open connection 'dflt_server_con': 1049 Unknown database 'mysql' (the last lines may be the most important ones) Killing Possible Leftover Processes ===== sol9x86-5.0-max.log NDB ===== im_options_unset [ fail ] Errors are (from /PATH/mysqltest-time) : mysqltest: In included file "./include/im_check_os.inc": At line 1: Could not open connection 'dflt_server_con': 1049 Unknown database 'mysql' (the last lines may be the most important ones) Killing Possible Leftover Processes ===== intelxeon3-5.0-standard.log normal In previous builds, also in other "IM" tests on other platforms: 5.0.21: im_daemon_life_cycle hpita2-64bit-5.0-max.log NDB pegasos3-glibc23-5.0-max.log NDB 5.0.22: im_daemon_life_cycle granny-5.0-max.log NDB hpita2-64bit-5.0-max.log NDB sol9x86-5.0-cluster.log NDB sol9x86-5.0-max.log NDB im_options_set granny-5.0-max.log normal 5.0.23: im_options_unset hpita2-64bit-5.0-pro.log normal im_utils hp3750-64bit-5.0-debug.log normal 5.0.24 test build: im_options_unset hpita2-64bit-5.0-pro.log normal hpita2-64bit-5.0-standard.log normal im_utils hpita2-64bit-5.0-pro.log normal How to repeat: Occurred during the test suite.