and notify user to re-execute a test in a couple minutes. Also, implement deleting the local testIsRunning file flag if this DNS related error occurs.
An alternative approach would be to programmatically implement a retry after a delay on runTest if the DNS related error (with message getaddrinfo ENOTFOUND) occurs. A programmatic retry approach wasn't selected since this issue only occurs on initial cluster configuration and if the user is fast enough to beat the DNS configuration process, which is a small portion of the total cluster lifetime.
and notify user to re-execute a test in a couple minutes. Also, implement deleting the local testIsRunning file flag if this DNS related error occurs.
An alternative approach would be to programmatically implement a retry after a delay on runTest if the DNS related error (with message
getaddrinfo ENOTFOUND) occurs. A programmatic retry approach wasn't selected since this issue only occurs on initial cluster configuration and if the user is fast enough to beat the DNS configuration process, which is a small portion of the total cluster lifetime.