[
https://issues.apache.org/jira/browse/WHIRR-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135282#comment-13135282
]
Andrei Savu commented on WHIRR-410:
-----------------------------------
I think that the automatic AMI selection works a bit different in 1.2.1. With
the following change the integration tests are working as expected:
{code}
---
core/src/main/java/org/apache/whirr/service/jclouds/TemplateBuilderStrategy.java
+++
core/src/main/java/org/apache/whirr/service/jclouds/TemplateBuilderStrategy.java
@@ -33,6 +33,7 @@ public class TemplateBuilderStrategy {
if (clusterSpec.getImageId() != null) {
templateBuilder.imageId(clusterSpec.getImageId());
} else {
+ templateBuilder.os64Bit(true);
templateBuilder.osFamily(OsFamily.UBUNTU);
templateBuilder.osVersionMatches("10.04");
{code}
> Review automatic image selection
> --------------------------------
>
> Key: WHIRR-410
> URL: https://issues.apache.org/jira/browse/WHIRR-410
> Project: Whirr
> Issue Type: Bug
> Reporter: Andrei Savu
> Fix For: 0.7.0
>
>
> While I was testing WHIRR-400 I have noticed that the ZooKeeper integration
> tests are failing on aws-ec2 with the automatically selected AMI but they are
> working as expected with the Amazon Linux AMI. The tests are also working as
> expected on cloudservers-us. This makes me think the failure is not related
> to our code changes and we should look for an external factor as the root
> cause.
> As part of this issue we should think about how to improve the automatic AMI
> selection mechanism in order to make it more robust and less likely to fail
> due to AMI upgrades and other external changes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
