| Bug #49195 | Some config TCs get 'Failed to get the version string of the cluster in use' | ||
|---|---|---|---|
| Submitted: | 30 Nov 2009 8:17 | Modified: | 1 Dec 2009 8:12 |
| Reporter: | Gunn Olaussen | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Tests: Cluster Manager | Severity: | S7 (Test Cases) |
| Version: | r1080 | OS: | Any |
| Assigned to: | Gunn Olaussen | CPU Architecture: | Any |
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.020 sec. using MySQL 8.0.36-u3-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2024, Oracle Corporation and/or its affiliates
Description: Test checks version string of cluster to find out whether a test case can be run (for those requiring a specific version), but there is another variant of the version string which is not matched by the pattern in the test framework. How to repeat: Run funcCLIResetConfigs on 6.3.20 or do "/usr/local/cluster-mgt/cluster-6.3.20/bin/ndbd --version" which gives: MySQL distrib mysql-5.1.30 ndb-6.3.20-GA, for pc-solaris2.10 (x86_64) Suggested fix: Add an optional part after the cluster version number with dash and then optional letters ("-GA")