libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Müller (JIRA) <j...@apache.org>
Subject [jira] [Created] (LIBCLOUD-529) ParamikoSSHClient path handling issue on windows
Date Tue, 11 Mar 2014 22:21:46 GMT
Stefan Müller created LIBCLOUD-529:
--------------------------------------

             Summary: 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)

Mime
View raw message