You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Geoff Macartney (JIRA)" <ji...@apache.org> on 2017/01/19 17:46:26 UTC

[jira] [Created] (BROOKLYN-427) JcloudsLocation is not releasing its customizers

Geoff Macartney created BROOKLYN-427:
----------------------------------------

             Summary: JcloudsLocation is not releasing its customizers
                 Key: BROOKLYN-427
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-427
             Project: Brooklyn
          Issue Type: Bug
            Reporter: Geoff Macartney
            Priority: Minor


preRelease and postRelease of JcloudsLocationCustomizers are not being 
called as expected during the release of a Jclouds machine location.

The problem is that the "setup" used in JcloudsLocation.obtainOnce includes a copy of the flags passed from MachineLifecycleEffectorTasks#stopAnyProvisionedMachines,
which includes the customizers. However, the "setup" used in the "release"
method of JcloudsLocation is taken from the JcloudsLocation itself, which
is the provisioning (i.e. parent) location, which doesn't have those 
customizers in it. 

It would actually make more sense to get the location customizers from
the machine location, as a given parent could have mutiple machines
with different customizers. 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)