Open youngbupark opened 4 months ago
:wave: @youngbupark Thanks for filing this bug report.
A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.
For more information on our triage process please visit our triage overview
:+1: We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
This has recurred 3-4 times in the past few months so could be a candidate for retry.
Steps to reproduce
When functional test deployed TF recipe, it failed because TF init was failed by the external issue.
In this issue, Radius tries to run
tf init
with k8s secret store tf state storage, buttf init
step was failed because k8s API server was not able to do TLS handshake. There are numerous reasons for this problem, but for this case, adding retry fortf init
might be able to mitigate the failures.For example,
Observed behavior
No response
Desired behavior
No error
Workaround
No response
rad Version
edge
Operating system
No response
Additional context
No response
Would you like to support us?
AB#11703