You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2010/09/30 23:23:32 UTC
[jira] Created: (WHIRR-107) Test failing due to not matching Amazon
Linux AMI on EC2
Test failing due to not matching Amazon Linux AMI on EC2
--------------------------------------------------------
Key: WHIRR-107
URL: https://issues.apache.org/jira/browse/WHIRR-107
Project: Whirr
Issue Type: Bug
Components: service/hadoop
Reporter: Tom White
Assignee: Tom White
Attachments: WHIRR-107.patch
When I run the Hadoop tests on trunk I get a failure because the ubuntu-alphas-us/karmic-i386-alpha5.manifest.xml AMI is being selected, rather than the Amazon Linux AMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WHIRR-107) Test failing due to not matching
Amazon Linux AMI on EC2
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916838#action_12916838 ]
Adrian Cole commented on WHIRR-107:
-----------------------------------
The default template for ec2 in jclouds-1.0-beta-7, is fixed at amazon linux. The only thing that could explain this would be a classpath problem.
http://github.com/jclouds/jclouds/blob/1.0-beta-7/aws/core/src/main/java/org/jclouds/aws/ec2/compute/config/EC2ComputeServiceContextModule.java
@Override
protected TemplateBuilder provideTemplate(Injector injector, TemplateBuilder template) {
String provider = injector.getInstance(Key.get(String.class, Provider.class));
if ("eucalyptus".equals(provider))
return template.osFamily(CENTOS);
else if ("nova".equals(provider))
return template.osFamily(UBUNTU);
else
return template.osFamily(AMZN_LINUX).os64Bit(true);
}
I don't recommend committing this patch. I do recommend investigating the setup that produced ubuntu, as this hints strongly of beta-6 classes in the classpath.
> Test failing due to not matching Amazon Linux AMI on EC2
> --------------------------------------------------------
>
> Key: WHIRR-107
> URL: https://issues.apache.org/jira/browse/WHIRR-107
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.2.0
>
> Attachments: WHIRR-107.patch
>
>
> When I run the Hadoop tests on trunk I get a failure because the ubuntu-alphas-us/karmic-i386-alpha5.manifest.xml AMI is being selected, rather than the Amazon Linux AMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-107) Test failing due to not matching Amazon
Linux AMI on EC2
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-107:
----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've just committed this.
> Test failing due to not matching Amazon Linux AMI on EC2
> --------------------------------------------------------
>
> Key: WHIRR-107
> URL: https://issues.apache.org/jira/browse/WHIRR-107
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.2.0
>
> Attachments: WHIRR-107.patch, WHIRR-107.patch
>
>
> When I run the Hadoop tests on trunk I get a failure because the ubuntu-alphas-us/karmic-i386-alpha5.manifest.xml AMI is being selected, rather than the Amazon Linux AMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-107) Test failing due to not matching Amazon
Linux AMI on EC2
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-107:
----------------------------
Attachment: WHIRR-107.patch
This patch fixes the problem for me.
> Test failing due to not matching Amazon Linux AMI on EC2
> --------------------------------------------------------
>
> Key: WHIRR-107
> URL: https://issues.apache.org/jira/browse/WHIRR-107
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.2.0
>
> Attachments: WHIRR-107.patch
>
>
> When I run the Hadoop tests on trunk I get a failure because the ubuntu-alphas-us/karmic-i386-alpha5.manifest.xml AMI is being selected, rather than the Amazon Linux AMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-107) Test failing due to not matching Amazon
Linux AMI on EC2
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-107:
----------------------------
Status: Patch Available (was: Open)
Fix Version/s: 0.2.0
> Test failing due to not matching Amazon Linux AMI on EC2
> --------------------------------------------------------
>
> Key: WHIRR-107
> URL: https://issues.apache.org/jira/browse/WHIRR-107
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.2.0
>
> Attachments: WHIRR-107.patch
>
>
> When I run the Hadoop tests on trunk I get a failure because the ubuntu-alphas-us/karmic-i386-alpha5.manifest.xml AMI is being selected, rather than the Amazon Linux AMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WHIRR-107) Test failing due to not matching
Amazon Linux AMI on EC2
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916892#action_12916892 ]
Tom White commented on WHIRR-107:
---------------------------------
This is only a problem with the Hadoop test (Cassandra and ZooKeeper are fine, they use a micro instance), which uses a m1.small instance. This doesn't support 64 bit - I wonder if that's causing this?
> Test failing due to not matching Amazon Linux AMI on EC2
> --------------------------------------------------------
>
> Key: WHIRR-107
> URL: https://issues.apache.org/jira/browse/WHIRR-107
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.2.0
>
> Attachments: WHIRR-107.patch
>
>
> When I run the Hadoop tests on trunk I get a failure because the ubuntu-alphas-us/karmic-i386-alpha5.manifest.xml AMI is being selected, rather than the Amazon Linux AMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WHIRR-107) Test failing due to not matching
Amazon Linux AMI on EC2
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916894#action_12916894 ]
Adrian Cole commented on WHIRR-107:
-----------------------------------
ahh I see.
right. then, this patch will do.. the only problem is that it will choose a 32bit ami even on micro, which supports 64bit. If that isn't a problem, then go ahead and commit.
> Test failing due to not matching Amazon Linux AMI on EC2
> --------------------------------------------------------
>
> Key: WHIRR-107
> URL: https://issues.apache.org/jira/browse/WHIRR-107
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.2.0
>
> Attachments: WHIRR-107.patch
>
>
> When I run the Hadoop tests on trunk I get a failure because the ubuntu-alphas-us/karmic-i386-alpha5.manifest.xml AMI is being selected, rather than the Amazon Linux AMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-107) Test failing due to not matching Amazon
Linux AMI on EC2
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-107:
----------------------------
Attachment: WHIRR-107.patch
bq. the only problem is that it will choose a 32bit ami even on micro, which supports 64bit.
Hadoop doesn't (currently) work on micro, if/when if does we can revisit this. I've updated the patch so that this logic is in HadoopTemplateBuilderStrategy, since it is specific to Hadoop.
> Test failing due to not matching Amazon Linux AMI on EC2
> --------------------------------------------------------
>
> Key: WHIRR-107
> URL: https://issues.apache.org/jira/browse/WHIRR-107
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.2.0
>
> Attachments: WHIRR-107.patch, WHIRR-107.patch
>
>
> When I run the Hadoop tests on trunk I get a failure because the ubuntu-alphas-us/karmic-i386-alpha5.manifest.xml AMI is being selected, rather than the Amazon Linux AMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.