[jira] [Resolved] (JCLOUDS-367) Second instance in a group has its inboundPorts ignored (Google Compute Engine)

["Andrew Phillips (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCLOUDS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Phillips resolved JCLOUDS-367.
-------------------------------------

    Resolution: Fixed

> Second instance in a group has its inboundPorts ignored (Google Compute Engine)
> -------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-367
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-367
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-labs-google
>    Affects Versions: 1.6.3
>            Reporter: Richard Downer (Cloudsoft)
>             Fix For: 1.6.3
>
>         Attachments: JCLOUDS-367-1.6.x.patch, JCLOUDS-367.tar.bz2
>
>
> Create the first instance with set of inbound ports A - works as expected.
> Create a second instance, with a different set of inbound ports B. This instance will have set A, not set B.
> For example:
>             GoogleComputeEngineTemplateOptions options = computeService.templateOptions()
>                     .as(GoogleComputeEngineTemplateOptions.class)
>                     .inboundPorts(22)
>                     ;
>             Set<? extends NodeMetadata> nodes1 = computeService.createNodesInGroup(GROUP_NAME, 1, options);
>             nodes.addAll(nodes1);
>             
>             options.inboundPorts(44);
>             Set<? extends NodeMetadata> nodes2 = computeService.createNodesInGroup(GROUP_NAME, 1, options);
>             nodes.addAll(nodes2);
>             
> In this example, nodes2 instance will have port 22 open, but not port 44.
> Full test case to follow in a moment. I will investigate the cause and hope to propose a fix soon!



--
This message was sent by Atlassian JIRA
(v6.1#6144)