-
Bug
-
Resolution: Fixed
-
High
-
None
-
4
-
Severity 3 - Minor
-
1
-
Summary
Occasionally Elastic Agent creation calls fail with the error Invalid Base64 encoding of user data
Expected Results
All elastic Agent calls succeed with creation of a new Elastic Agent
Actual Results
Occasionally the creation attempt will fail:
The below exception is thrown in the xxxxxxx.log file:
com.amazonaws.services.ec2.model.AmazonEC2Exception: Invalid BASE64 encoding of user data (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterValue; Request ID: 24be1899-d089-48a5-b658-559d39a2034b)
Workaround
When failed, a new elastic agent call is made and the new agent starts normally.
Notes
it looks like when we use ava.util.Base64.getMimeEncoder().encodeToString(userData) to encode the userData for the instance (specifically the keypair generated per-instance) it is occasionally encoded with extra carriage returns which prevent proper decoding by AWS API.
- is cloned as
-
BDEV-15096 Loading...
[BAM-19945] Elastic Bamboo - Invalid Base64 encoding of user data
Remote Link | Original: This issue links to "BDEV-15096 (Jira)" [ 405415 ] | New: This issue links to "BDEV-15096 (Hello Jira)" [ 405415 ] |
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 2693944 ] | New: JAC Bug Workflow v3 [ 3386053 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Regular Expression | New: Invalid BASE64 encoding of user data |
I think Amazon fixed something, because spot instances in Bamboo 5.14.1 is working again.