jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Downer (Cloudsoft) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCLOUDS-367) Second instance in a group has its inboundPorts ignored (Google Compute Engine)
Date Wed, 06 Nov 2013 19:30:19 GMT
Richard Downer (Cloudsoft) created JCLOUDS-367:
--------------------------------------------------

             Summary: 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.7.0, 1.6.3


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)

Mime
View raw message