Group name not set for new nodes on EC2

Hi For some reason the new nodes I create on EC2 are missing the group names. NodeMetadata node = getOnlyElement(compute.createNodesInGroup(vmSettings.getGroupName(), 1, template)); logger.info("New node " + node.getId() + " " + concat(node.getPrivateAddresses(), node.getPublicAddresses())+" in

Re: Group name not set for new nodes on EC2

Yeah sure. This is my final code to create the security group: AWSEC2SecurityGroupExtension client = (AWSEC2SecurityGroupExtension)compute.getSecurityGroupExtension().get(); SecurityGroup sg = client.createSecurityGroup("crossbuild", CLOUD_REGION); Builder b =

Re: Group name not set for new nodes on EC2

Regarding the group name in the nodes, could you share the code you use to build the template, including the template options? Thanks for the additional details! More information on the resource prefixing Ignasi was mentioning is here, by the way:

Re: Group name not set for new nodes on EC2

Good to see that part is working! FWIW, jclouds adds a prefix to some resources, for convenience. This can be configured, though, by setting the ComputeServiceProperties.RESOURCENAME_PREFIX property [1] when creating the context. You can change the default "jclouds" value or set it to an empty

Re: Group name not set for new nodes on EC2

Thank you. I have already solved the security group issue. The problem was the "cosmetic" one I mentioned in the email on the end. I was creating a group with name "crossbuild" and tried to use the same name when creating the node. The exception was thrown when creating the node, not when

Re: Group name not set for new nodes on EC2

Regarding the group name in the nodes, could you share the code you use to build the template, including the template options? On 17 March 2016 at 01:52, Ignasi Barrera wrote: > Good to see that part is working! > > FWIW, jclouds adds a prefix to some resources, for convenience.