The Provisioning.pm::retrieve_image calls du on other management nodes via SSH to determine whether or not an image exists on the other management node. Since the image may reside in different locations on the other management node, multiple search paths are appended to the du command such as:
du -b /install/vmwarewinxp-myimage1-v0* /install/vmware_images/vmwarewinxp-myimage1-v0*
It is expected for some 'No such file' STDERR error output to be generated from the command since the image won't reside in all locations. There may also be STDOUT output generated if the image was found. STDOUT and STDERR normally get sorted out correctly because 2>&1 is appended to every SSH command issued. Otherwise, the 2 streams may get mixed together and the output can't be parsed correctly.
It seems as though the du command is executing itself multiple times when multiple search paths are entered, but 2>&1 isn't working correctly.
[root@my_mn]# ssh other_mn 'du -b /install/vmwarewinxp-myimage1-v0* /install/vmware_images/vmwarewinxp-myimage1-v0* 2>&1'
du: cannot access `/install/vmwarewinxp-myimage1-v0*': No such file or directory
du: cannot access `/install/vmwarewinxp-myimage1-v0*'13355723776 /install/vmware_images/vmwarewinxp-myimage1-v0