brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-259) jcloudsByon location spec leaks location instances
Date Mon, 09 May 2016 20:30:13 GMT


ASF GitHub Bot commented on BROOKLYN-259:

Github user johnmccabe commented on the pull request:
    Looks like we're not overriding the `null` credentials returned in the `NodeMetadata`
in JcloudsLocation.findNodeOrThrow. These should be getting replaced with the user/password
set in the `ConfigBag`.

> jcloudsByon location spec leaks location instances
> --------------------------------------------------
>                 Key: BROOKLYN-259
>                 URL:
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: Aled Sage
>             Fix For: 0.10.0
> When declaring in a location spec such as 
> {noformat}
> jcloudsByon(provider="aws-ec2",region="us-east-1",user="brooklyn",password="pa55w0rd",hosts="i-12345678")
> {noformat}
> It caused new locations to be created and persisted every few seconds, but for those
locations to be never deleted.
> ---
> This was caused by changes made in 0.9.0 to {{LocationResolver}} implementations, so
that it creates a {{LocationSpec}} rather than instantiating a location directly. Unfortunately,
{{JcloudsByonLocationResolver}} had not been updated. The REST api would poll this regularly
to find out about the types of location, and on every poll it would create new locations.
> This is similar to the problem encountered for localhost, fixed in time for 0.9.0 in

This message was sent by Atlassian JIRA

View raw message