Hi Zaid, thanks for reporting that. After some investigations, I think the problem is more general than `us-east-1` and should be fixed at https://github.com/jclouds/jclouds/pull/612. Notice, the fix has been applied to `master` and cherry-picked to jclouds-1.8.x and jclouds-1.7.x. In particular, jclouds now consider also more recent centos and ubuntu distro https://github.com/apache/jclouds/blob/master/compute/src/main/java/org/jclouds/compute/reference/ComputeServiceConstants.java#L89
On the brooklyn side, we need to decide if it's right to prefer for Ubuntu 14.04 over 12.04 and for CentOS 6.6 over 6 [1] Anyone disagree? Otherwise I'm going to issue a PR to change that. Best, Andrea [1]: https://github.com/apache/incubator-brooklyn/blob/0be9f25a5445f03798df3996eef3e8f5232eac1b/locations/jclouds/src/main/java/brooklyn/location/jclouds/BrooklynImageChooser.java#L114-L115 On 4 November 2014 14:02, Richard Downer <[email protected]> wrote: > Actually I think I have seen this recently... Ubuntu 12.04 (Precise) > now has a very long list of security updates that get installed by the > Java 'setup' task and I think Brooklyn may be timing out, especially > if it's a low-power instance. I've switched my brooklyn.properties to > use Ubuntu 14.04 and it seemed to help. I'll get a PR against the > website to update the recommended brooklyn.properties with the new AMI > IDs. > > Richard. > > On 27 October 2014 17:33, Zaid Mohsin <[email protected]> > wrote: > > Hi, when I tried to launch an entity that installs Java on the standard > jclouds:aws-ec2:us-east-1 it got stuck on the “setup” activity trying to > install java. Upon further investigation I think the culprit might have > been the default AMI > (ubuntu-precise-12.04-amd64-server-20140927.manifest.xml (ami-ecda6c84)). > When I used my own AMI (RightImage_CentOS_6.3_x64_v5.8.8.5.manifest.xml > (ami-7d7bfc14)), it worked just fine. > > > > Has anyone experienced something similar? > > > > Cheers >
