jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-987) AWS EC2: if specifying subnet ID, security groups are not created
Date Thu, 29 Oct 2015 00:55:27 GMT

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

ASF subversion and git services commented on JCLOUDS-987:

Commit 985d45122bc55f6ddf2e3e36f9aac0dca6abd3cf in jclouds's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=985d451 ]

JCLOUDS-987: Create security groups in AWS if subnetId is specified

> AWS EC2: if specifying subnet ID, security groups are not created
> -----------------------------------------------------------------
>                 Key: JCLOUDS-987
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-987
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.9.0
>            Reporter: Richard Downer
>            Assignee: Ignasi Barrera
>              Labels: aws-ec2
> If the template options for an EC2 instance specify a subnet ID, then jclouds will not
create any security groups.
> This is defined in this piece of code:
> https://github.com/jclouds/jclouds/blob/master/providers/aws-ec2/src/main/java/org/jclouds/aws/ec2/compute/strategy/CreateKeyPairPlacementAndSecurityGroupsAsNeededAndReturnRunOptions.java#L182
> The if statement checks if subnet has been set; the "false" part causes security groups
to be created, but the "true" part does not - therefore if the subnet ID is set there are
no security groups created.
> The workaround is for the user to define the security groups ahead of time and specify
the security group IDs in the template options.

This message was sent by Atlassian JIRA

View raw message