aws-cloudformation / aws-cloudformation/aws-cloudformation-resource-providers-awsutilities-commandrunner
Command Runner occasionally throws SSLError
- Dominant language
- Java
- Stars
- 81
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I have been experiencing consistently an issue during the morning where command runner is throwing an SSLError.
I have a command that installs aws cli v2, so that in the same command I can use timestream-write to insert a dummy record into a Timestream table during deployment for schema enforcement (since I have scheduled query against the table).
This is the partial output of `cloud-init-output.log`
As can be seen, output is empty.
I have not changed anything about the command itself and it was succeeding before this error started happening and then started succeeding again after an hour or two of re-trying it. I experienced first success after failures, after deploying from a local machine when it suddenly started working, then re-tested by redeploying from devops machine and it started succeeding after that, thus I suspect I didn't do anything to fix this.
The `cfn-wire.log` doesn't seem to have anything of interest (1 line for 200 response code from cloudformation).
The `cfn-init.log` has this error:
Even though it started working again, I am afraid that if we try to do deployment in production we will experience the same issue.
Is there any known fix for this or is it a bug in command runner?
Contributor guide
Research direction
Start by reviewing the reported cloud-init-output.log, cfn-wire.log, and cfn-init.log alongside the deployment command that installs AWS CLI v2 and writes to Timestream. Reproduce the intermittent failure if possible and determine whether the TLS error originates in command runner or an external dependency. Done means the cause and a reliable fix or documented workaround are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100