Why my Bamboo AWS Instance is suddently deleted?
Asked by Juan Ignacio Onetto:

Hi I use BAmboo OnDemand. I have verified all possible configurations to avoid having suddenly delete my Bamboo instance. Can someone help me identify what is causing my instance to be removed or deleted?

I really appreciate any help!

This is my current configuration. Let me know if I am missing something

Elastic Bamboo global settings {#toc-hId-1681672876}
----------------------------------------------------

\<label style="color: #505050; float: left; display: block; left: -140px; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>AWS Region\</label\>US East (Northern Virginia)  
\<label style="color: #505050; float: left; display: block; left: -140px; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>Maximum number of elastic instances\</label\>1  
\<label style="color: #505050; float: left; display: block; left: -140px; margin-right: -130px; padding-top: 4px; position: relative; width: 130px; text-align: right;"\>Automatic shutdown\</label\>EC2 instances will *not* be automatically terminated.  

Automatic elastic instance management {#toc-hId--870484085}
-----------------------------------------------------------

EC2 instances must be *manually* created and terminated as needed.


Answers:
author: Juan Ignacio Onetto
body: I am not sure if there is any. When I asked Eric I always got the same answer, to instance data with EBS volumes. Hope you find some work around!


author: Eric Delente
body: We need MS deploy for our instances, and while it's not terribly complex to add that, it's not terribley convenient either. Is the only way around this to create an EBS volume?


author: Juan Ignacio Onetto
body: Hi. I can see in the audit log that when the instance is deleted I get these entries. Any help?:

TimestampUserChanged fieldOld valueNew value

First Previous Showing 1-50 of 191 Next Last

01:12 AM, Sun, 15 SepSYSTEMunconfigurableFeatureDefaults.outer-class.bambooPermissionManager.sync.state20

01:12 AM, Sun, 15 SepSYSTEMunconfigurableFeatureDefaults.outer-class.bambooPermissionManager.sync.result\[@class\]dynamic-proxy


author: Juan Ignacio Onetto
body: Sorry for the HTML. Here again:

Elastic Bamboo global settings

AWS RegionUS East (Northern Virginia)

Maximum number of elastic instances1

Automatic shutdownEC2 instances will not be automatically terminated.

comments: author: Eric Delente
body: I am having the same problem - did you get any help with this?


author: Juan Ignacio Onetto
body: This is what ive got from support. And I ended up doing the EBS external storage stuff....

-------

Hi Juan,

There are occasions where EC2 instance will be shutdown by Bamboo even there's no configuration that allowed this to happen. The most common is whenever Bamboo get restarted, all EC2 instance will get disconnected and will be shutdown automatically since Bamboo can't recover the connection after restart - OnDemand instance will have at least one maintenance every week on Monday.

Another occasion would be that Bamboo lost connection to the EC2 instance even it is not restarted.

If you really want to have an EC2 instance ready for your builds, you can always schedule Bamboo to start a number of instances here - <https://colppy.atlassian.net/builds/admin/elastic/schedule/viewElasticInstanceSchedules.action>

Hope this helps.

Regards,  
Fahd


Tags: community