[RFC PATCH datacenter-manager 1/4] server: connection: multi client: use correct client error for retrying

[Dominik Csapak <d.csapak@proxmox.com>]

Since commit
 8e3b1f06 (client: split out Connect error and factor out error classification)
in the proxmox workspace, Connection errors are split out to it's own
type of `proxmox_client::Error`s. Since then, every connection error
was returned normally and not retried via other hosts from the remote
config.

Use the correct error type to only retry when the actual connection is
not working, not if the api or the server returns an issue.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
Not sure if just changing this is a good idea, or if we want to catch
both connect and client errors? tracking only connect errors seemed
the correct way to me here, but maybe someone has a different opinion.

 server/src/connection.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/server/src/connection.rs b/server/src/connection.rs
index 93f173e6..28e4799f 100644
--- a/server/src/connection.rs
+++ b/server/src/connection.rs
@@ -744,7 +744,7 @@ macro_rules! try_request {
 
                 let request = client.$how($method.clone(), $path_and_query, params.as_ref());
                 match tokio::time::timeout($self.timeout, request).await {
-                    Ok(Err(proxmox_client::Error::Client(err))) => {
+                    Ok(Err(proxmox_client::Error::Connect(err))) => {
                         last_err = Some(err);
                     }
                     Ok(result) => {
-- 
2.47.3