| Bug #80423 | ndb.ndbinfo_upgrade clobbers datadir | ||
|---|---|---|---|
| Submitted: | 18 Feb 2016 8:54 | Modified: | 18 Feb 2016 18:38 |
| Reporter: | Magnus Blåudd | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | 7.4.11 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[18 Feb 2016 18:38]
Jon Stephens
Fixed in NDB 7.4.11/7.5.1. Affects testing only. No user-facing changes to document. Closed.
Description: The ndbinfo_upgrade test cases runs mysql_upgrade which leaves behind a file as a marker showing that the datadir has been upgraded to be created in the mysqld data dir. This file thus clobbers the datadir and shoudl be removed as part of the test. If not remove it will caused a subsequent run of ndbinfo_upgrade to fail since the mysql_upgrade invocation errors out due to "already upgraded". How to repeat: ./mtr ndbinfo_upgrade ndbinfo_upgrade ndb.ndbinfo_upgrade [ pass ] 978 ndb.ndbinfo_upgrade [ fail ] Test ended at 2016-02-18 09:53:32 CURRENT_TEST: ndb.ndbinfo_upgrade mysqltest: At line 35: command "$MYSQL_UPGRADE --skip-verbose > $log_file 2>&1" failed Suggested fix: Remove the upgrade infor marker file as part of test. This is done by other tests running mysql_upgrade.