Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

bamboo-agent-release-eu-w1/7.0.0-rc1 - Not propagated



We are having problem with the bamboo 7.0.0-rc1 release. 

First of all Bamboo is not following docker versioning schema as any other Atlassian product. You can not specify major version like Jira or confluence so we had to use latest and it has been working fine until rc version has been pushed as latest (never happened before).

Issue with the release is that elastic agents won't start with the following error:

2020-01-20 09:01:53,874 INFO [main] [S3Synchroniser] Fetching the list of remote objects...

2020-01-20 09:01:53,946 INFO [main] [S3Synchroniser] Found 0 files in s3://bamboo-agent-release-eu-w1/7.0.0-rc1/47bbccebf635531c0cd588c3fae4e28882e96ecfc3c336a92cfe67c33a57af51

2020-01-20 09:01:53,947 INFO [main] [S3Synchroniser] Found 36 files in /opt/bamboo-elastic-agent

2020-01-20 09:01:53,948 INFO [main] [S3Synchroniser] Generating the list of files to fetch from S3...

2020-01-20 09:01:53,948 INFO [main] [S3Synchroniser] Generating the list of files to remove...

2020-01-20 09:01:53,958 INFO [main] [S3Synchroniser] Removing 0 files from /opt/bamboo-elastic-agent

2020-01-20 09:01:53,958 INFO [main] [S3Synchroniser] Fetching 0 files to /opt/bamboo-elastic-agent

2020-01-20 09:01:53,958 INFO [main] [S3Synchroniser] Fetched 0 MB from S3

2020-01-20 09:01:53,959 FATAL [main] [ElasticAgentInstaller] No jars found in /opt/bamboo-elastic-agent/boot - it probably means that the assembly (bamboo-agent-release-eu-w1/7.0.0-rc1/47bbccebf635531c0cd588c3fae4e28882e96ecfc3c336a92cfe67c33a57af51/) has not been propagated to this region. Contact Atlassian support.


Could you please help with the resolution?

1 answer

1 accepted

1 vote
Answer accepted


Please try again, we had an issue with migration to some regions. 

Thank you!

It's working fine now.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events