You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2015/11/02 13:05:27 UTC

[jira] [Commented] (JCLOUDS-1033) DigitalOcean v2 should not fail if no private key has been provided

    [ https://issues.apache.org/jira/browse/JCLOUDS-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985109#comment-14985109 ] 

Ignasi Barrera commented on JCLOUDS-1033:
-----------------------------------------

Patch: https://github.com/jclouds/jclouds-labs/pull/220

> DigitalOcean v2 should not fail if no private key has been provided
> -------------------------------------------------------------------
>
>                 Key: JCLOUDS-1033
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1033
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-labs
>    Affects Versions: 1.9.1
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>              Labels: digitalocean
>
> The DigitalOcean v2 provider fails if there is no key pair auto-generation and the user does not provide a login private key. This might seem correct, but makes it impossible to use the ssh-agent to authenticate.
> The failure should be replaced by a warning message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)