-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
None
-
Affects Version/s: None
-
Component/s: Elastic Bamboo
-
Severity 3 - Minor
Summary
If an elastic agent fails to connect to S3, Bamboo runs a "route" command. However, we often see this fail.
Environment
- Bamboo Elastic Agent
Steps to reproduce
- Start an Elastic agent with an IP outside of the whitelisted range
Expected Results
Agent starts as expected
Actual Results
The below exception is thrown in the bamboo-elastic-agent.out file:
2017-10-17 00:56:09,188 ERROR [main] [ElasticAgentInstaller] Unable to access S3 bucket, dumping the route table: 2017-10-17 00:56:09,188 INFO [main] [ElasticAgentInstaller] Starting [route, -n] Exception in thread "main" java.io.IOException: Cannot run program "route": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at com.atlassian.bamboo.agent.elastic.installer.ElasticAgentInstaller.runCommand(ElasticAgentInstaller.java:135) at com.atlassian.bamboo.agent.elastic.installer.ElasticAgentInstaller.dumpRouteTable(ElasticAgentInstaller.java:125) at com.atlassian.bamboo.agent.elastic.installer.ElasticAgentInstaller.install(ElasticAgentInstaller.java:84) at com.atlassian.bamboo.agent.elastic.installer.ElasticAgentInstaller.main(ElasticAgentInstaller.java:199) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:248) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 4 more
There should be better logging messages to reduce back-and-forth communications between customers and Support Engineers.
- relates to
-
BAM-18681 IPs should be automatically whitelisted when Amazon adds a new IP range
- Gathering Interest