Restart of failed YADE file transfers does not work

Current Situation

If a YADE transfer fails and the order is suspended in the job chain node that startet the transfer it is possible to restart the transfer from the JOC Cockpit in the File Transfer View. Doing this an error occurs The original transfer order cannot be determined.. The reason for this is that in the DB table YADE_TRANSFERS the column JOB_CHAIN_NODE is null.

Desired Behavior

The restart of a failed YADE transfer should work.

Test Instruction to reproduce the problem

• Prepare test configuration
  • Set up a YADE file transfer configuration e.g. SFTP for a copy operation
• Prepare test data
  • Then prepare three files 1.txt, 2.txt, 3.txt to be transferred
  • In the target environment create a file 3.txt and remove write permissions for all users
• Perform the test case
  • The transfer result should include that the files 1.txt and 2.txt are transferred successfully and the file 3.txt fails. Therefore the transfer is considered being failed.
• Verify test results
  • In the JOC Cockpit the failed transfer should be visible including 2 successful and 1 failed file.
  • To reproduce the error try to repeat the transfer for the failed file. This should result in the error message from the above issue description.

Test Instruction to verify the resolution

• Perform above steps for test configuration and test data. Perform test case as indicated.
• Verify test results
  • To check the resolution of this issue
    • apply the attached patch by storing the file to the ./lib/patches directory of a JobScheduler Master and
    • restart the Master.
    • Then restart the transfer for the failed file.
  • This time the transfer for file 3.txt should be repeated.

Maintainer Note

This Issue has been introduced with YADE-522.