[
https://issues.apache.org/jira/browse/VCL-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Kurth resolved VCL-688.
----------------------------
Resolution: Fixed
> Image retrieval may fail to detect image residing on another management node
> ----------------------------------------------------------------------------
>
> Key: VCL-688
> URL: https://issues.apache.org/jira/browse/VCL-688
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Affects Versions: 2.3
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Priority: Minor
> Fix For: 2.4
>
>
> 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.
> Command:
> [root@my_mn]# ssh other_mn 'du -b /install/vmwarewinxp-myimage1-v0*
> /install/vmware_images/vmwarewinxp-myimage1-v0* 2>&1'
> Expected output:
> du: cannot access `/install/vmwarewinxp-myimage1-v0*': No such file or
> directory
> 13355723776 /install/vmware_images/vmwarewinxp-myimage1-v0
> Actual output:
> du: cannot access `/install/vmwarewinxp-myimage1-v0*'13355723776
> /install/vmware_images/vmwarewinxp-myimage1-v0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
