Bug #52883 testBackup and testSystemRestart uses ssh directly
Submitted: 16 Apr 2010 10:12
Reporter: Jørgen Austvik Email Updates:
Status: Verified Impact on me:
None 
Category:Tests: Cluster Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[16 Apr 2010 10:12] Jørgen Austvik
Description:
testBackup  uses ssh directyl, which is troublesome on Windows and generally bad design.

Jorgen Austvik - Sun Norway wrote:
> === modified file 'storage/ndb/test/ndbapi/testBackup.cpp'
> --- storage/ndb/test/ndbapi/testBackup.cpp      2009-05-27 15:21:45 +0000
> +++ storage/ndb/test/ndbapi/testBackup.cpp      2010-04-08 11:37:22 +0000
> @@ -782,6 +782,10 @@
>
>  int main(int argc, const char** argv){
>    ndb_init();
> +#ifdef _WINDOWS
> +  // Skip this test on windows, as it uses ssh directly
> +  return NDBT_ProgramExit(NDBT_OK);
> +#endif
>    NDBT_TESTSUITE_INSTANCE(testBackup);
>    return testBackup.execute(argc, argv);
>  }

When checking the log files from atrt run with angel I find that testSystemRestart also uses the NdbBackup class in the test case SR_DD_3b_LCP, so this limitation affects more testcases.

What seems to be missing is a "remote rm -rf <path>" command and it shouldn't be to hard to get that into cpcd but how would the testcase know where to find cpcd? Of course it has hostname and could maybe default to port 1234. 

How to repeat:
Run ATRT tests on Windows

Suggested fix:
ACRT additions?