brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-427) JcloudsLocation is not releasing its customizers
Date Wed, 25 Jan 2017 19:46:26 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838442#comment-15838442
] 

ASF GitHub Bot commented on BROOKLYN-427:
-----------------------------------------

Github user geomacy closed the pull request at:

    https://github.com/apache/brooklyn-server/pull/530


> 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)

Mime
View raw message