Description of problem: When there is no executing host (may happen when hosts go no responsive during a command execution for example), the StorageJobCallback may fail with NPE when attempting to check the host status. How reproducible: Always - with debugger (otherwise it's very hard to reproduce). Steps to Reproduce: 1. Have a 4.1 DC with 2 domains and one host. 2. Create a disk 3. Attempt to move the disk 4. Before the copyData operation is executed disconnect the connection between the engine and the host Actual results: StorageJobCallback will fail with NPE when attempting to check the host status. Expected results: The StorageJobCallback should treat the job as failed as it was never submitted to a host. Additional info:
The following scenario was tested with devel in debug Steps to Reproduce: 1. Have a 4.1 DC with 2 domains and one host. 2. Create a disk 3. Attempt to move the disk 4. Before the copyData operation is executed disconnect the connection between the engine and the host ->>>> No NPE and job is failed by engine Moving to VERIFIED!