brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Otto (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BROOKLYN-229) Get IllegalArgumentException by the use of the keypair parameter in namelocation
Date Tue, 23 Feb 2016 16:18:18 GMT
Felix Otto created BROOKLYN-229:
-----------------------------------

             Summary: Get IllegalArgumentException by the use of the keypair parameter in
namelocation
                 Key: BROOKLYN-229
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-229
             Project: Brooklyn
          Issue Type: Bug
    Affects Versions: 0.8.0
            Reporter: Felix Otto


For any new ec2 instance automatically a new key pair will be generated in AWS by the jcloud
implementation. After some research we find out that it is possible to set the keypair in
the named location of the brooklyn.properties file. If we set the keypair in the named location
than we get the following error:

log:

{code}
java.lang.IllegalArgumentException: no private key configured for: {region=eu-central-1, name=01-brooklyn};
please use options.overrideLoginCredentialWith(rsa_private_text)
{code}

brooklyn.properties:
{code}
brooklyn.location.named.aws-frankfurt= jclouds:aws-ec2:eu-central-1
brooklyn.location.named.aws-frankfurt.displayName=AWS Frankfurt (ida-01-brooklyn)
brooklyn.location.named.aws-frankfurt.identity=<ACCESSKEY_ID>
brooklyn.location.named.aws-frankfurt.credential=<SECRET_ACCESSKEY_ID>
brooklyn.location.named.aws-frankfurt.keyPair=01-brooklyn
brooklyn.location.named.aws-frankfurt.privateKeyFile=/home/ubuntu/.ssh/id_rsa
brooklyn.location.named.aws-frankfurt.publicKeyFile=/home/ubuntu/.ssh/id_rsa.pub
{code}

This cause for this problem can be found in the class org.jclouds.ec2.compute.strategy.CreateKeyPairAndSecurityGroupsAsNeededAndReturnRunOptions
line 128



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

Mime
View raw message