[
https://issues.apache.org/jira/browse/LIBCLOUD-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050767#comment-13050767
]
Tomaz Muraus commented on LIBCLOUD-93:
--------------------------------------
Yeah, that is the problem my original patch tried to fix (besides making the
code more readable and clear).
The problem was that if the SSH server has not been started yet when the node
came online, the deployment task was never executed because by default, SSH
client has a large timeout which means it never even tried to reconnect.
In any case, I have pushed some changes to trunk which should hopefully fix
this problem. I still need to write tests to make sure it works properly in all
the edge cases.
> Failure reported for successful deployment
> ------------------------------------------
>
> Key: LIBCLOUD-93
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-93
> Project: Libcloud
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.5.0
> Environment: Ubuntu 10.10, Python 2.6.6
> Reporter: Michael Mior
> Labels: deployment
>
> When creating a couple simple deploy scripts with the Rackspace driver,
> libcloud reports a failure to provision. However, if I check my account, the
> node was created and when I log in, I see all the scripts have executed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
