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?
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.logAs 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.logdoesn't seem to have anything of interest (1 line for 200 response code from cloudformation).The
cfn-init.loghas 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?