Closed yaegor closed 1 year ago
This would be helpful, we see this with some frequency:
"[https://prod.vault.com:443/v1/auth/approle/teamcity/root/login":](https://prod.vault.com/v1/auth/approle/teamcity/root/login%22:) Connect to prod.vault.com:443 [prod.vault.com/, prod.vault.com/, prod.vault.com/] failed: connect timed out; nested exception is org.apache.http.conn.ConnectTimeoutException: Connect to prod.vault.com:443 [prod.vault.com/, prod.vault.com2, prod.vault.com7] failed: connect timed out, see teamcity-server.log for details
Thanks for the reminder on this! We've created a task for it on Youtrack: TW-81838
If request to Vault fails, it makes sense to retry before failing the build. This is probbaly actual for the server and agent operations.
BTW, in case of the network errors, it would make sense to include the original error in the build log message.
Here is an example of the failing agent operation: Build log:
Agent log: