You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ron-savoia reported getting the following errors with a federated clusters using mTLS:
2022-10-28T20:33:32.124Z [WARN] nomad.rpc: failed TLS handshake: remote_addr=192.168.1.190:55376 error="remote error: tls: bad certificate"
2022-10-28T20:33:32.755Z [WARN] nomad.stats_fetcher: error getting server health: server=server1.west error="rpc error: failed to get conn: x509: certificate is valid for server.west.nomad, localhost, not server.east.nomad"
But normal federated operations such as submitting a job across regions works as expected, so the mTLS configuration itself is fine. The stats_fetcher code was updated when we did the autopilot update in 1.4.0 in #14441. The RPCs involved here should be doing the same cross-region checks as other federated RPCs. But taking a quick look at the code, it's not clear to me that we should be making cross-region stats-fetcher requests at all here either.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
@ron-savoia reported getting the following errors with a federated clusters using mTLS:
But normal federated operations such as submitting a job across regions works as expected, so the mTLS configuration itself is fine. The
stats_fetcher
code was updated when we did the autopilot update in 1.4.0 in #14441. The RPCs involved here should be doing the same cross-region checks as other federated RPCs. But taking a quick look at the code, it's not clear to me that we should be making cross-region stats-fetcher requests at all here either.The text was updated successfully, but these errors were encountered: