A problem to set-up the Elastic bamboo in jira-studio
Asked by I.K. Lim:

To Jira-supporter,

I have a problem to set-up the Elastic bamboo in jira-studio. I used the default AMI.

|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [Large - Fedora 8](https://udptech.jira.com/builds/admin/elastic/image/configuration/viewElasticImageConfiguration.action?configurationId=196609 "A Fedora 8 64bit elastic image configuration with 7.5GB RAM and 4 EC2 compute units")(default) | ami-395a8550 | No EBS | Large | Default (chosen by EC2) | [0](https://udptech.jira.com/builds/admin/elastic/image/configuration/viewElasticInstancesForConfiguration.action?configurationId=196609) | [Start](https://udptech.jira.com/builds/admin/elastic/prepareElasticInstances.action?elasticImageConfigurationId=196609) \| [Disable](https://udptech.jira.com/builds/admin/elastic/image/configuration/disableElasticImageConfiguration.action?configurationId=196609) \| [View](https://udptech.jira.com/builds/admin/elastic/image/configuration/viewElasticImageConfiguration.action?returnUrl=%2Fadmin%2Felastic%2Fimage%2Fconfiguration%2FviewElasticImageConfigurations.action&configurationId=196609) \| [Edit](https://udptech.jira.com/builds/admin/elastic/image/configuration/editElasticImageConfiguration.action?returnUrl=%2Fadmin%2Felastic%2Fimage%2Fconfiguration%2FviewElasticImageConfigurations.action&configurationId=196609) |

When I start this AMI, it fails.

**Elastic Bamboo Error: *EC2 Instance failed to start: EC2 instance order failed.***

(com.xerox.amazonws.ec2.EC2Exception : Client error : The requested instance type's architecture (x86_64) does not match the architecture in the manifest for ami-395a8550 (i386))

(07 May 2012, 10:26:00 AM, Occurrences: 6 )

[View error details](https://udptech.jira.com/builds/admin/viewError.action?buildKey=Elastic%20Bamboo&error=3) [Clear error from log](https://udptech.jira.com/builds/admin/removeErrorFromLog.action?buildKey=Elastic%20Bamboo&error=3&returnUrl=/admin/elastic/manageElasticInstances.action)

|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| May 4, 2012 5:41:16 PM Elastic instance transitioned from STARTING to FAILED_TO_START.                                                                                                          |
| May 4, 2012 5:41:16 PM Detected that the elastic instance has stopped.                                                                                                                          |
| May 4, 2012 5:49:20 PM Requested that new elastic instance be created for configuration: Large - Fedora 8                                                                                       |
| May 4, 2012 5:49:20 PM Elastic instance transitioned from STARTING to FAILED_TO_START.                                                                                                          |
| May 4, 2012 5:49:20 PM Detected that the elastic instance has stopped.                                                                                                                          |
| May 4, 2012 5:57:05 PM Currently there are no agents that can build TC-TCTEST-JOB1-1 available. New elastic instance that can build it will be started (providing the configuration allows it). |
| May 4, 2012 5:57:05 PM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.                                                               |
| May 4, 2012 5:57:06 PM Requested that new elastic instance be created for configuration: Large - Fedora 8                                                                                       |
| May 4, 2012 5:57:06 PM Elastic instance transitioned from STARTING to FAILED_TO_START.                                                                                                          |
| May 4, 2012 5:57:06 PM Detected that the elastic instance has stopped.                                                                                                                          |

I tested the other AMI(ami-78b15411) just for the test. It works very well. But this AMI is useless because it hasn't Bamboo.

I guess it is a kind of configuration bug and I think that only you can solve the problem.

I.K. Lim/CTO

UDP Technology, Ltd.


Answers:
author: Przemek Bruski
body: In your image configuration, you need to choose an [instances type](http://aws.amazon.com/ec2/instance-types/) that provides sufficient resources for your build and supports 32bit images. Large instance is 64bit only.


author: TimT
body: The default AMI provided with Bamboo is intended for a 32-bit VM, and it looks like you have tried to create a 64-bit instance.

Do you actually require a 64-bit architecture? If so, your only option will be to create a custom image, and install the elastic agent on that yourself.


author: JIRA Admin(Not Used)
body: Thank you for your help. I solve the problem \^\^.


author: JIRA Admin(Not Used)
body: I don't require a 64-bit architecure. Could you tell me how to select a 32-bit instance in Elastic Bamboo configuration. I think the default Image(Larg-Fedora8) provided by attlassian is 64bit.

[Manage Elastic Image Configurations](https://udptech.jira.com/builds/admin/elastic/image/configuration/viewElasticImageConfigurations.action "Manage Elastic Image Configurations") ? Large - Fedora 8 (default) {#toc-hId-481534400}
======================================================================================================================================================================================================================================

Elastic Image Configuration {#toc-hId--438416382}
-------------------------------------------------

\<label style="color: #505050; float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>Name\</label\>Large - Fedora 8  
A Fedora 8 64bit elastic image configuration with 7.5GB RAM and 4 EC2 compute units  
\<label style="color: #505050; float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>AMI ID\</label\>ami-395a8550  
\<label style="color: #505050; float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>EBS Snapshot ID\</label\>No EBS  
\<label style="color: #505050; float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>Instance Type\</label\>Large  
\<label style="color: #505050; float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>Availability Zone Preference\</label\>Default (chosen by EC2)  
\<label style="color: #505050; float: left; display: block; left: -140px; line-height: 1; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>Active Instances\</label\>[0](https://udptech.jira.com/builds/admin/elastic/image/configuration/viewElasticInstancesForConfiguration.action?configurationId=196609)


Tags: cloud