[
https://issues.apache.org/jira/browse/LIBCLOUD-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931587#comment-13931587
]
Tomaz Muraus commented on LIBCLOUD-529:
---------------------------------------
That's a good catch, thanks.
I think a reasonable fix is to always just use forward slash as a path
separator since this should always work with SSH.
I will work on a fix later today.
> ParamikoSSHClient path handling issue on windows
> ------------------------------------------------
>
> Key: LIBCLOUD-529
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-529
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Environment: apache-libcloud 0.14.1, Windows 7
> Reporter: Stefan Müller
>
> In the method {{compute.ssh.ParamikoSSHClient.put(..)}} the current directory
> (on the remote machine) is concatenated with the file name using
> {{os.path.join}} (aliased as {{pjoin}}.
> If libcloud is used on Windows (local machine not the remote node), this will
> use a backslash as separator. Paramiko expects all paths with unix-style
> {{/}} separators independent of the platform (see comment on
> https://github.com/paramiko/paramiko/issues/278)
> The problem can be reproduced with {{ScriptDeployment}}. If the {{name}}
> argument is not an absolute path, it will fail. It will try to execute
> {{/root\libcloud_deployment_xxx.sh}}. Linux will think this is an escaped
> {{l}}, not a separator. The result is a file-not-found message on stderr.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
