[BROOKLYN-229] Get IllegalArgumentException by the use of the keypair parameter in a namedlocation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.0
• Fix Version/s: 0.9.0
• Assignee: Unassigned
• Reporter: Felix Otto
• Created: 23/Feb/16 16:17
• Updated: 06/Apr/16 16:26
• Resolved: 06/Apr/16 16:26

Description

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:

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

brooklyn.properties:

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

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