automation-suite
2024.10
true
Wichtig :
Bitte beachten Sie, dass dieser Inhalt teilweise mithilfe von maschineller Übersetzung lokalisiert wurde. Es kann 1–2 Wochen dauern, bis die Lokalisierung neu veröffentlichter Inhalte verfügbar ist.
UiPath logo, featuring letters U and I in white

Automation Suite in OpenShift – Installationsanleitung

Letzte Aktualisierung 12. Juni 2025

Ausführen des Diagnosetools

Das Automation Suite-Diagnosetool führt eine Reihe von Überprüfungen durch, um einen Bericht über den Zustand des Clusters zu erstellen, den Sie analysieren können, um Probleme und deren potenzielle Ursachen zu identifizieren. Das Tool hilft Ihnen bei der Suche nach häufigen Problemen, wie z. B. verlorene Datenbankkonnektivität oder ungültige bzw. abgelaufene Anmeldeinformationen.

Das Automation Suite-Diagnosetool ist sowohl in uipathctl als auch in uipathtools verfügbar, die sie auf Ihre Verwaltungsmaschine herunterladen können.

Anweisungen zum Herunterladen finden Sie unter uipathctl und uipathtools.

uipathtools ist ein CLI-Tool, das eine Teilmenge von uipathctl-Funktionen enthält, die für Integritätsbefehle spezifisch sind. Das Tool ist abwärtskompatibel und funktioniert mit allen unterstützten Versionen der Automation Suite. Wir empfehlen, uipathtools als ersten Schritt zu verwenden, wenn ein Problem auftritt.

Schnelle Validierung

Schnelle Validierung

Die Befehle check und test bieten schnelle Einblicke in den Status des Clusters, ohne eine eingehende Analyse durchzuführen.
  • check ist vom Integritäts- und Synchronisierungsstatus von ArgoCD abhängig und ändert keinen Status im Cluster
  • test sieht sich die Anwendungen, Bereitstellungen oder Pods an und ändert vorübergehend den Status des Clusters, um Ihnen diese Erkenntnisse zu liefern.

Zustandsprüfung

Um eine Zustandsprüfung durchzuführen, verwenden Sie einen der folgenden Befehle, je nachdem, welches CLI-Tool Sie verwenden:

  • Wenn Sie uipathctl verwenden, führen Sie Folgendes aus:
    ./uipathctl health check./uipathctl health check
  • Wenn Sie uipathtools verwenden, führen Sie Folgendes aus:
    ./uipathtools health check./uipathtools health check
Hinweis:
Verwenden Sie das Flag --namespace (optional), wenn Sie input.json nicht angeben. Sie müssen das Flag nur verwenden, wenn sich die Installation nicht im uipath -Namespace befindet. Ohne das Flag ruft die Zustandsprüfung Diagnosedaten aus allen Namespaces ab.

Beispielausgabe des generierten Berichts:

Checks run on cluster/
 ✔ [NOTIFICATIONSERVICE]
    ✔ [NOTIFICATIONSERVICE_HEALTH] Application is healthy and in sync
 ✔ [ACTION_CENTER]
    ✔ [ACTIONCENTER_HEALTH] Application is healthy and in sync
 ❌ [SYNC]
    ❌ [namespace:"uipath" | kind:"Application" | name:"dataservice"] Application health check failed: health status is Progressing and sync status is Synced
 ✔ [RELOADER]
    ✔ [RELOADER_HEALTH] Application is healthy and in sync
 ❌ [POD]
    ✔ [LIST_NAMESPACES] Retrieved 25 namespaces to check pod health
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-v5krg cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-xs9t5 cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-taskrunner-787df76c74-98h5l cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
 ✔ [ISTIO]
    ✔ [LIST_PODS] Found 2 pods for Istio
    ✔ [ISTIOD_EXISTS] The Istio pods are present and running version - 
    ✔ [ISTIOD_READY] Istio pods are healthy
 ✔ [AIEVENTS]
    ✔ [AIEVENTS_HEALTH] Application is healthy and in sync
 ❌ [DATASERVICE]
    ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced
 ✔ [PLATFORM]
    ✔ [PLATFORM_HEALTH] Application is healthy and in sync
 ✔ [WEBHOOK]
    ✔ [WEBHOOK_HEALTH] Application is healthy and in syncChecks run on cluster/
 ✔ [NOTIFICATIONSERVICE]
    ✔ [NOTIFICATIONSERVICE_HEALTH] Application is healthy and in sync
 ✔ [ACTION_CENTER]
    ✔ [ACTIONCENTER_HEALTH] Application is healthy and in sync
 ❌ [SYNC]
    ❌ [namespace:"uipath" | kind:"Application" | name:"dataservice"] Application health check failed: health status is Progressing and sync status is Synced
 ✔ [RELOADER]
    ✔ [RELOADER_HEALTH] Application is healthy and in sync
 ❌ [POD]
    ✔ [LIST_NAMESPACES] Retrieved 25 namespaces to check pod health
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-v5krg cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-xs9t5 cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-taskrunner-787df76c74-98h5l cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
 ✔ [ISTIO]
    ✔ [LIST_PODS] Found 2 pods for Istio
    ✔ [ISTIOD_EXISTS] The Istio pods are present and running version - 
    ✔ [ISTIOD_READY] Istio pods are healthy
 ✔ [AIEVENTS]
    ✔ [AIEVENTS_HEALTH] Application is healthy and in sync
 ❌ [DATASERVICE]
    ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced
 ✔ [PLATFORM]
    ✔ [PLATFORM_HEALTH] Application is healthy and in sync
 ✔ [WEBHOOK]
    ✔ [WEBHOOK_HEALTH] Application is healthy and in sync
Standardmäßig führt der Befehl uipathctl health check Zustandsprüfungen für alle Komponenten aus. Er ermöglicht Ihnen jedoch auch, genau die Komponenten zu überprüfen, an denen Sie interessiert sind:
  • Wenn Sie Komponenten von der Ausführung ausschließen möchten, verwenden Sie das Flag --excluded. Wenn Sie beispielsweise den Zustand von SQL nicht überprüfen möchten, führen Sie uipathctl health check --excluded SQL aus. Der Befehl überprüft den Zustand aller Komponenten mit Ausnahme von SQL.
  • Wenn Sie nur bestimme Komponenten in die Ausführung einschließen möchten, verwenden Sie das Flag --included. Wenn Sie beispielsweise nur das DNS und den Objektspeicher überprüfen möchten, führen Sie uipathctl health check --included DNS,OBJECTSTORAGE aus.
Hinweis:

Hier finden Sie die Namen der Komponenten, die Sie in die Zustandsprüfungen ein- oder ausschließen können. In diesem Beispiel stellt das erste Wort auf jeder eingerückten Zeile den Komponentennamen dar. Beispiel: SQL, OBJECTSTORE, DNS usw.

Analysieren der Protokolle

  1. Nach dem Ausführen einer Zustandsüberprüfung zeigen die Protokolle, dass die Zustandsprüfung für die Data Service-Anwendung fehlgeschlagen ist.
    ❌ [DATASERVICE]
    ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced❌ [DATASERVICE]
    ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced
  2. Nach weiteren Untersuchungen wird klar, dass die Data Service-Anwendung fehlgeschlagen ist, da sich die Pods dataservice-runtime-8f5bb7d56-v5krg und dataservice-taskrunner-787df76c74-98h5l in einem fehlerhaften Zustand befinden. Bei einer weiteren Analyse stellen Sie fest, dass das fehlende dataservice-external-storage-secret fehlt.
    ❌ [POD]
    ✔ [LIST_NAMESPACES] Retrieved 25 namespaces to check pod health
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-v5krg cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-xs9t5 cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-taskrunner-787df76c74-98h5l cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found❌ [POD]
    ✔ [LIST_NAMESPACES] Retrieved 25 namespaces to check pod health
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-v5krg cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-xs9t5 cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-taskrunner-787df76c74-98h5l cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
  3. Um dieses Problem zu beheben, stellen Sie sicher, dass Sie die richtigen Anmeldeinformationen für den Objektspeicher in der input.jsonangegeben haben.

    Weitere Informationen finden Sie unter Aktualisieren von Anmeldeinformationen.

Integritätstest

Um einen Integritätstest auszuführen, verwenden Sie je nach CLI-Tool einen der folgenden Befehle:

  • Wenn Sie uipathctl verwenden, führen Sie Folgendes aus:
    ./uipathctl health test./uipathctl health test
  • Wenn Sie uipathtools verwenden, führen Sie Folgendes aus:
    ./uipathtools health test./uipathtools health test
Hinweis:
Verwenden Sie das Flag --namespace (optional), wenn Sie input.json nicht angeben. Sie müssen das Flag nur verwenden, wenn sich die Installation nicht im uipath -Namespace befindet.

Beispielausgabe des generierten Berichts:

Checks run on cluster/
 ✔ [ACTION_CENTER]
    ✔ [CREATE_NAMESPACE] Created namespace prereqk6b72
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqk6b72
    ✔ [CREATE_NAMESPACE] Created namespace prereqbxjx8
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqbxjx8
    ✔ [CREATE_NAMESPACE] Created namespace prereq8zvw4
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq8zvw4
 ✔ [DATASERVICE]
    ✔ [CREATE_NAMESPACE] Created namespace prereqxwlsb
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqxwlsb
    ✔ [CREATE_NAMESPACE] Created namespace prereq5szsn
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq5szsn
 ✔ [APPS]
    ✔ [CREATE_NAMESPACE] Created namespace prereq9z6nb
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq9z6nb
    ✔ [CREATE_NAMESPACE] Created namespace prereq6v7lm
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq6v7lm
    ✔ [CREATE_NAMESPACE] Created namespace prereqxxn5v
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqxxn5v
 ✔ [AUTOMATION_HUB]
    ✔ [CREATE_NAMESPACE] Created namespace prereq4jkbt
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq4jkbt
 ✔ [TEST_MANAGER]
    ✔ [CREATE_NAMESPACE] Created namespace prereqnvvpc
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqnvvpc
 ✔ [ORCHESTRATOR]
    ✔ [CREATE_NAMESPACE] Created namespace prereq8pf2f
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq8pf2f
    ✔ [CREATE_NAMESPACE] Created namespace prereq4w4v4
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq4w4v4
    ✔ [CREATE_NAMESPACE] Created namespace prereqkzwqg
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqkzwqg
 ✔ [INSIGHTS]
    ✔ [CREATE_NAMESPACE] Created namespace prereqqmgjc
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqqmgjc
    ✔ [CREATE_NAMESPACE] Created namespace prereq4vnjx
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq4vnjx
    ✔ [CREATE_NAMESPACE] Created namespace prereqgtg9g
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqgtg9g
 ✔ [AUTOMATION_OPS]
    ✔ [CREATE_NAMESPACE] Created namespace prereqgkkrz
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqgkkrz
 ✔ [AICENTER]
    ✔ [CREATE_NAMESPACE] Created namespace prereqdls88
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqdls88
    ✔ [CREATE_NAMESPACE] Created namespace prereq6m7x9
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq6m7x9Checks run on cluster/
 ✔ [ACTION_CENTER]
    ✔ [CREATE_NAMESPACE] Created namespace prereqk6b72
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqk6b72
    ✔ [CREATE_NAMESPACE] Created namespace prereqbxjx8
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqbxjx8
    ✔ [CREATE_NAMESPACE] Created namespace prereq8zvw4
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq8zvw4
 ✔ [DATASERVICE]
    ✔ [CREATE_NAMESPACE] Created namespace prereqxwlsb
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqxwlsb
    ✔ [CREATE_NAMESPACE] Created namespace prereq5szsn
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq5szsn
 ✔ [APPS]
    ✔ [CREATE_NAMESPACE] Created namespace prereq9z6nb
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq9z6nb
    ✔ [CREATE_NAMESPACE] Created namespace prereq6v7lm
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq6v7lm
    ✔ [CREATE_NAMESPACE] Created namespace prereqxxn5v
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqxxn5v
 ✔ [AUTOMATION_HUB]
    ✔ [CREATE_NAMESPACE] Created namespace prereq4jkbt
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq4jkbt
 ✔ [TEST_MANAGER]
    ✔ [CREATE_NAMESPACE] Created namespace prereqnvvpc
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqnvvpc
 ✔ [ORCHESTRATOR]
    ✔ [CREATE_NAMESPACE] Created namespace prereq8pf2f
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq8pf2f
    ✔ [CREATE_NAMESPACE] Created namespace prereq4w4v4
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq4w4v4
    ✔ [CREATE_NAMESPACE] Created namespace prereqkzwqg
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqkzwqg
 ✔ [INSIGHTS]
    ✔ [CREATE_NAMESPACE] Created namespace prereqqmgjc
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqqmgjc
    ✔ [CREATE_NAMESPACE] Created namespace prereq4vnjx
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq4vnjx
    ✔ [CREATE_NAMESPACE] Created namespace prereqgtg9g
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqgtg9g
 ✔ [AUTOMATION_OPS]
    ✔ [CREATE_NAMESPACE] Created namespace prereqgkkrz
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqgkkrz
 ✔ [AICENTER]
    ✔ [CREATE_NAMESPACE] Created namespace prereqdls88
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereqdls88
    ✔ [CREATE_NAMESPACE] Created namespace prereq6m7x9
    ✔ [CREATE_POD] Created test pod curl-pod in namespace prereq6m7x9
Standardmäßig führt der Befehl uipathctl health test Zustandsprüfungen für alle Komponenten aus. Er ermöglicht Ihnen jedoch auch, genau die Komponenten zu überprüfen, an denen Sie interessiert sind:
  • Wenn Sie Komponenten von der Ausführung ausschließen möchten, verwenden Sie das Flag --excluded. Wenn Sie beispielsweise den Zustand von SQL nicht überprüfen möchten, führen Sie uipathctl health test --excluded SQL aus. Der Befehl überprüft den Zustand aller Komponenten mit Ausnahme von SQL.
  • Wenn Sie nur bestimme Komponenten in die Ausführung einschließen möchten, verwenden Sie das Flag --included. Wenn Sie beispielsweise nur das DNS und den Objektspeicher überprüfen möchten, führen Sie uipathctl health test --included DNS,OBJECTSTORAGE aus.
Hinweis:

Hier finden Sie die Namen der Komponenten, die Sie in die Integritätstests ein- oder ausschließen können. In diesem Beispiel stellt das erste Wort auf jeder eingerückten Zeile den Komponentennamen dar. Beispiel: SQL, OBJECTSTORE, DNS usw.

Hinweis:
Wenn Sie die Ausgabe der Befehle check und test für die Data Service-Anwendung vergleichen, können Sie sehen, dass erstere den Zustand der Anwendung validiert, während letztere das Routing überprüft.

Bekanntes Problem

Möglicherweise erhalten Sie eine Fehlermeldung ähnlich dem folgenden Beispiel. Sie können dies ignorieren, da keine Actions erforderlich sind.

E0621 23:32:56.426321   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded
E0621 23:32:56.426392   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded
E0621 23:32:56.444420   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded
E0621 23:32:56.446150   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded
E0621 23:32:56.513357   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceededE0621 23:32:56.426321   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded
E0621 23:32:56.426392   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded
E0621 23:32:56.444420   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded
E0621 23:32:56.446150   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded
E0621 23:32:56.513357   24470 reflector.go:138] external/io_k8s_client_go/tools/cache/reflector.go:167: Failed to watch *v1.Pod: context deadline exceeded

Umfassende Validierung

Umfassende Validierung

Der diagnose -Befehl bietet detaillierte Einblicke in den Status des Clusters. Es hilft Ihnen, Probleme auf allen Ebenen zu identifizieren, z. B. SQL, Objektspeicher, Knoten, Secret, Istio, Netzwerk usw.
  • Sie deckt sowohl die Befehle check als auch test ab.
  • Es führt die Voraussetzungsprüfungen durch, die vor der Installation der Automation Suite durchgeführt wurden, um Änderungen an der Umgebungskonfiguration zu validieren, die nach der Installation vorgenommen wurden und die eine potenzielle Ursache für das Problem sein können.

  • Es wird auf allen Knoten ausgeführt, um alle knotenspezifischen Probleme zu sammeln, z. B. die Nichtverfügbarkeit von Ressourcen, Netzwerkinterferenzen usw.

Um eine Diagnoseprüfung auszuführen, verwenden Sie je nach CLI-Tool einen der folgenden Befehle:

  • Wenn Sie uipathctl verwenden, führen Sie Folgendes aus:
    ./uipathctl health diagnose input.json --versions version.json./uipathctl health diagnose input.json --versions version.json
  • Wenn Sie uipathtools verwenden, führen Sie Folgendes aus:
    ./uipathtools health diagnose input.json --versions version.json./uipathtools health diagnose input.json --versions version.json
Hinweis:
Verwenden Sie das Flag --namespace (optional), wenn Sie input.json nicht angeben. Sie müssen das Flag nur verwenden, wenn sich die Installation nicht im uipath -Namespace befindet. Ohne das Flag werden Diagnosedaten aus allen Namespaces abgerufen.

Beispielausgabe des generierten Berichts:

Ran cluster/ checks...
    ❌ [DATASERVICE]
       ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced
    ❌ [ISTIO]
       ✔ [ISTIO_SYNC_STATUS] Istio sync is up-to-date
       ❌ [ISTIO_ENVOY_CONFIG_STATUS] Istio Envoy configs are not healthy: Error [IST0101] (VirtualService uipath/du-platform-vs) Referenced host:port not found: "aistorage:5000"
       ✔ [ISTIO_SERVICEMESH_VALIDATION_GET_REGISTRY_FQDN] Successfully retrieved registry url
       ✔ [ISTIO_SERVICEMESH_VALIDATION_GET_CLUSTER_FQDN] Successfully retrieved cluster fqdn
       ✔ [ISTIO_SERVICEMESH_VALIDATION_CREATE_TEST_DEPLOYMENT] Successfully created the test deployment istio-validation-deployment
       ✔ [ISTIO_SERVICEMESH_VALIDATION_CREATE_TEST_SERVICE] Successfully created the test service istio-validation-service
       ✔ [ISTIO_SERVICEMESH_VALIDATION_CREATE_TEST_GATEWAY] Successfully created the test gateway istio-validation-gateway
       ✔ [ISTIO_SERVICEMESH_VALIDATION_CREATE_TEST_VIRTUALSERVICE] Successfully created the test virtual service istio-validation-vs
       ✔ [ISTIO_SERVICEMESH_VALIDATION_URL_ACCESS] Success exposing the service via servicemesh
    ❌ [POD]
       ✔ [LIST_NAMESPACES] Retrieved 25 namespaces to check pod health
       ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/ah-tenant-service-sync-insights-data-job-28122960-p6rzg cannot mount volume: MountVolume.SetUp failed for volume "ah-insights-secrets" : failed to sync secret cache: timed out waiting for the condition
       ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-v5krg cannot mount volume: (combined from similar events): Unable to attach or mount volumes: unmounted volumes=[external-storage-creds], unattached volumes=[workload-socket is-secrets openssl istio-podinfo temp-location cert-location istio-data external-storage-creds workload-certs istio-envoy java domain-cert-config edk2 credential-socket tmp additional-ca-cert-config pem istiod-ca-cert istio-token app-secrets ceph-storage-creds]: timed out waiting for the condition
       ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-xs9t5 cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
       ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-taskrunner-787df76c74-98h5l cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
       ❌ [POD_UNHEALTHY] Latest event for pod uipath/du-documentmanager-dm-maintenance-cron-28122960-4sm5z: Error: failed to sync configmap cache: timed out waiting for the condition
    ❌ [SYNC]
       ❌ [namespace:"uipath" | kind:"Application" | name:"dataservice"] Application health check failed: health status is Progressing and sync status is Synced
    Ran MAINTENANCE checks...
        ✔ successful
    Ran NODE checks...
        ✔ successful
    Ran REPLICAS checks...
        ✔ successful
Checks complete!
Checks complete!
Ran local/ checks...
    Ran ARGO checks...
        ✔ successful
    Ran CONNECTIVITY checks...
     ⚠ [CONNECTIVITY]
        ⚠ [NETWORK_TEST_SETUP] Failed to create the network test infrastructure: failed to create echo-host-role role: error creating role: roles.rbac.authorization.k8s.io "network-prereq-9thz9-echo-host-role" is forbidden: user "system:serviceaccount:os7140768:uipathadmin" (groups=["system:serviceaccounts" "system:serviceaccounts:os7140768" "system:authenticated"]) is attempting to grant RBAC permissions not currently held:
{APIGroups:["security.openshift.io"], Resources:["securitycontextconstraints"], ResourceNames:["hostnetwork-v2"], Verbs:["use"]}
    Ran DEPLOYMENT_PROFILE checks...
        ✔ successful
    Ran DNS(FQDN=APPS.<FQDN>) checks...
        ✔ successful
    Ran DNS(FQDN=INSIGHTS.<FQDN>) checks...
        ✔ successful
    Ran INGRESS checks...
        ✔ successful
    Ran NAMESPACE checks...
        ✔ successful
    Ran NETWORK-POLICIES checks...
        ✔ successful
    Ran NODE(CPU >= 8, RAM >= 16G) checks...
     ⚠ [NODE(CPU >= 8, RAM >= 16G)]
        ✔ [LIST_NODES] Listed 4 nodes
        ✔ [AT_LEAST_ONE_NODE] At least one node found
        ✔ [CPU_USAGE] Node os7140768-7db2g-master-0 has 62.50% CPU usage
        ✔ [MEMORY_USAGE] Node os7140768-7db2g-master-0 has 49.09% memory usage
        ✔ [POD_USAGE] Node os7140768-7db2g-master-0 has 0.00% of pods in use. Number of pods: 0.00 max allowed: 250.00
        ✔ [CPU_CAPACITY(os7140768-7db2g-master-0)] Node has enough CPU capacity. Has: 8, needs at least: 8
        ✔ [RAM_CAPACITY(os7140768-7db2g-master-0)] Node has enough RAM capacity. Has: 32868564Ki, needs at least: 16G
        ✔ [CPU_USAGE] Node os7140768-7db2g-worker-eastus1-l6c5p has 18.75% CPU usage
        ✔ [MEMORY_USAGE] Node os7140768-7db2g-worker-eastus1-l6c5p has 22.31% memory usage
        ✔ [POD_USAGE] Node os7140768-7db2g-worker-eastus1-l6c5p has 7.60% of pods in use. Number of pods: 19.00 max allowed: 250.00
        ✔ [CPU_CAPACITY(os7140768-7db2g-worker-eastus1-l6c5p)] Node has enough CPU capacity. Has: 16, needs at least: 8
        ✔ [RAM_CAPACITY(os7140768-7db2g-worker-eastus1-l6c5p)] Node has enough RAM capacity. Has: 65847764Ki, needs at least: 16G
        ✔ [CPU_USAGE] Node os7140768-7db2g-worker-eastus2-p89lq has 18.75% CPU usage
        ✔ [MEMORY_USAGE] Node os7140768-7db2g-worker-eastus2-p89lq has 26.30% memory usage
        ✔ [POD_USAGE] Node os7140768-7db2g-worker-eastus2-p89lq has 7.20% of pods in use. Number of pods: 18.00 max allowed: 250.00
        ✔ [CPU_CAPACITY(os7140768-7db2g-worker-eastus2-p89lq)] Node has enough CPU capacity. Has: 16, needs at least: 8
        ✔ [RAM_CAPACITY(os7140768-7db2g-worker-eastus2-p89lq)] Node has enough RAM capacity. Has: 65847764Ki, needs at least: 16G
        ✔ [CPU_USAGE] Node os7140768-7db2g-worker-eastus3-d6jj5 has 18.75% CPU usage
        ✔ [MEMORY_USAGE] Node os7140768-7db2g-worker-eastus3-d6jj5 has 17.91% memory usage
        ✔ [POD_USAGE] Node os7140768-7db2g-worker-eastus3-d6jj5 has 6.80% of pods in use. Number of pods: 17.00 max allowed: 250.00
        ✔ [CPU_CAPACITY(os7140768-7db2g-worker-eastus3-d6jj5)] Node has enough CPU capacity. Has: 16, needs at least: 8
        ✔ [RAM_CAPACITY(os7140768-7db2g-worker-eastus3-d6jj5)] Node has enough RAM capacity. Has: 65847764Ki, needs at least: 16G
        ⚠ [AS_ROBOTS_NODE_EXISTS] No dedicated node found
    Ran OSS(COMPONENT=CERT-MANAGER) checks...
        ✔ successful
    Ran OSS(COMPONENT=GATEKEEPER) checks...
        ✔ successful
    Ran OSS(COMPONENT=ISTIO) checks...
        ✔ successful
    Ran PERMISSION checks...
        ✔ successful
    Ran PRIORITYCLASS checks...
        ✔ successful
    Ran REGISTRY_PULL checks...
        ✔ successful
    Ran RESOURCE checks...
        ✔ successful
    Ran SECRETS checks...
        ✔ successful
    Ran STORAGECLASS(NAME=STORAGE_CLASS) checks...
        ✔ successful
    Ran STORAGECLASS(NAME=STORAGE_CLASS_SINGLE_REPLICA) checks...
        ✔ successful
Ran cluster/ checks...
    Ran ORCHESTRATOR(CLASSIC_FOLDERS) checks...
        ✔ successful
Ran nodes/ checks...
Ran CONTROLPLANECONNECTIVITY checks...
 ✔ 4/4 nodes successful
Ran DNS(FQDN=APPS.<FQDN>) checks...
 ✔ 4/4 nodes successful
Ran DNS(FQDN=INSIGHTS.<FQDN>) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=BA) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=DATASERVICE) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=ORCHESTRATOR) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=PLATFORM) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=TESTMANAGER) checks...
 ✔ 4/4 nodes successful
Ran REDIS(PORT=6380) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=ASROBOTS, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=AUTOMATIONHUB, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=AUTOMATIONOPS, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=BA, TYPE=ODBC) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=DATASERVICE, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=INSIGHTS, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=NOTIFICATIONSERVICE, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=ORCHESTRATOR, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=PLATFORM, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=TESTMANAGER, TYPE=ADO) checks...
 ✔ 4/4 nodes successfulRan cluster/ checks...
    ❌ [DATASERVICE]
       ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced
    ❌ [ISTIO]
       ✔ [ISTIO_SYNC_STATUS] Istio sync is up-to-date
       ❌ [ISTIO_ENVOY_CONFIG_STATUS] Istio Envoy configs are not healthy: Error [IST0101] (VirtualService uipath/du-platform-vs) Referenced host:port not found: "aistorage:5000"
       ✔ [ISTIO_SERVICEMESH_VALIDATION_GET_REGISTRY_FQDN] Successfully retrieved registry url
       ✔ [ISTIO_SERVICEMESH_VALIDATION_GET_CLUSTER_FQDN] Successfully retrieved cluster fqdn
       ✔ [ISTIO_SERVICEMESH_VALIDATION_CREATE_TEST_DEPLOYMENT] Successfully created the test deployment istio-validation-deployment
       ✔ [ISTIO_SERVICEMESH_VALIDATION_CREATE_TEST_SERVICE] Successfully created the test service istio-validation-service
       ✔ [ISTIO_SERVICEMESH_VALIDATION_CREATE_TEST_GATEWAY] Successfully created the test gateway istio-validation-gateway
       ✔ [ISTIO_SERVICEMESH_VALIDATION_CREATE_TEST_VIRTUALSERVICE] Successfully created the test virtual service istio-validation-vs
       ✔ [ISTIO_SERVICEMESH_VALIDATION_URL_ACCESS] Success exposing the service via servicemesh
    ❌ [POD]
       ✔ [LIST_NAMESPACES] Retrieved 25 namespaces to check pod health
       ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/ah-tenant-service-sync-insights-data-job-28122960-p6rzg cannot mount volume: MountVolume.SetUp failed for volume "ah-insights-secrets" : failed to sync secret cache: timed out waiting for the condition
       ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-v5krg cannot mount volume: (combined from similar events): Unable to attach or mount volumes: unmounted volumes=[external-storage-creds], unattached volumes=[workload-socket is-secrets openssl istio-podinfo temp-location cert-location istio-data external-storage-creds workload-certs istio-envoy java domain-cert-config edk2 credential-socket tmp additional-ca-cert-config pem istiod-ca-cert istio-token app-secrets ceph-storage-creds]: timed out waiting for the condition
       ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-xs9t5 cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
       ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-taskrunner-787df76c74-98h5l cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
       ❌ [POD_UNHEALTHY] Latest event for pod uipath/du-documentmanager-dm-maintenance-cron-28122960-4sm5z: Error: failed to sync configmap cache: timed out waiting for the condition
    ❌ [SYNC]
       ❌ [namespace:"uipath" | kind:"Application" | name:"dataservice"] Application health check failed: health status is Progressing and sync status is Synced
    Ran MAINTENANCE checks...
        ✔ successful
    Ran NODE checks...
        ✔ successful
    Ran REPLICAS checks...
        ✔ successful
Checks complete!
Checks complete!
Ran local/ checks...
    Ran ARGO checks...
        ✔ successful
    Ran CONNECTIVITY checks...
     ⚠ [CONNECTIVITY]
        ⚠ [NETWORK_TEST_SETUP] Failed to create the network test infrastructure: failed to create echo-host-role role: error creating role: roles.rbac.authorization.k8s.io "network-prereq-9thz9-echo-host-role" is forbidden: user "system:serviceaccount:os7140768:uipathadmin" (groups=["system:serviceaccounts" "system:serviceaccounts:os7140768" "system:authenticated"]) is attempting to grant RBAC permissions not currently held:
{APIGroups:["security.openshift.io"], Resources:["securitycontextconstraints"], ResourceNames:["hostnetwork-v2"], Verbs:["use"]}
    Ran DEPLOYMENT_PROFILE checks...
        ✔ successful
    Ran DNS(FQDN=APPS.<FQDN>) checks...
        ✔ successful
    Ran DNS(FQDN=INSIGHTS.<FQDN>) checks...
        ✔ successful
    Ran INGRESS checks...
        ✔ successful
    Ran NAMESPACE checks...
        ✔ successful
    Ran NETWORK-POLICIES checks...
        ✔ successful
    Ran NODE(CPU >= 8, RAM >= 16G) checks...
     ⚠ [NODE(CPU >= 8, RAM >= 16G)]
        ✔ [LIST_NODES] Listed 4 nodes
        ✔ [AT_LEAST_ONE_NODE] At least one node found
        ✔ [CPU_USAGE] Node os7140768-7db2g-master-0 has 62.50% CPU usage
        ✔ [MEMORY_USAGE] Node os7140768-7db2g-master-0 has 49.09% memory usage
        ✔ [POD_USAGE] Node os7140768-7db2g-master-0 has 0.00% of pods in use. Number of pods: 0.00 max allowed: 250.00
        ✔ [CPU_CAPACITY(os7140768-7db2g-master-0)] Node has enough CPU capacity. Has: 8, needs at least: 8
        ✔ [RAM_CAPACITY(os7140768-7db2g-master-0)] Node has enough RAM capacity. Has: 32868564Ki, needs at least: 16G
        ✔ [CPU_USAGE] Node os7140768-7db2g-worker-eastus1-l6c5p has 18.75% CPU usage
        ✔ [MEMORY_USAGE] Node os7140768-7db2g-worker-eastus1-l6c5p has 22.31% memory usage
        ✔ [POD_USAGE] Node os7140768-7db2g-worker-eastus1-l6c5p has 7.60% of pods in use. Number of pods: 19.00 max allowed: 250.00
        ✔ [CPU_CAPACITY(os7140768-7db2g-worker-eastus1-l6c5p)] Node has enough CPU capacity. Has: 16, needs at least: 8
        ✔ [RAM_CAPACITY(os7140768-7db2g-worker-eastus1-l6c5p)] Node has enough RAM capacity. Has: 65847764Ki, needs at least: 16G
        ✔ [CPU_USAGE] Node os7140768-7db2g-worker-eastus2-p89lq has 18.75% CPU usage
        ✔ [MEMORY_USAGE] Node os7140768-7db2g-worker-eastus2-p89lq has 26.30% memory usage
        ✔ [POD_USAGE] Node os7140768-7db2g-worker-eastus2-p89lq has 7.20% of pods in use. Number of pods: 18.00 max allowed: 250.00
        ✔ [CPU_CAPACITY(os7140768-7db2g-worker-eastus2-p89lq)] Node has enough CPU capacity. Has: 16, needs at least: 8
        ✔ [RAM_CAPACITY(os7140768-7db2g-worker-eastus2-p89lq)] Node has enough RAM capacity. Has: 65847764Ki, needs at least: 16G
        ✔ [CPU_USAGE] Node os7140768-7db2g-worker-eastus3-d6jj5 has 18.75% CPU usage
        ✔ [MEMORY_USAGE] Node os7140768-7db2g-worker-eastus3-d6jj5 has 17.91% memory usage
        ✔ [POD_USAGE] Node os7140768-7db2g-worker-eastus3-d6jj5 has 6.80% of pods in use. Number of pods: 17.00 max allowed: 250.00
        ✔ [CPU_CAPACITY(os7140768-7db2g-worker-eastus3-d6jj5)] Node has enough CPU capacity. Has: 16, needs at least: 8
        ✔ [RAM_CAPACITY(os7140768-7db2g-worker-eastus3-d6jj5)] Node has enough RAM capacity. Has: 65847764Ki, needs at least: 16G
        ⚠ [AS_ROBOTS_NODE_EXISTS] No dedicated node found
    Ran OSS(COMPONENT=CERT-MANAGER) checks...
        ✔ successful
    Ran OSS(COMPONENT=GATEKEEPER) checks...
        ✔ successful
    Ran OSS(COMPONENT=ISTIO) checks...
        ✔ successful
    Ran PERMISSION checks...
        ✔ successful
    Ran PRIORITYCLASS checks...
        ✔ successful
    Ran REGISTRY_PULL checks...
        ✔ successful
    Ran RESOURCE checks...
        ✔ successful
    Ran SECRETS checks...
        ✔ successful
    Ran STORAGECLASS(NAME=STORAGE_CLASS) checks...
        ✔ successful
    Ran STORAGECLASS(NAME=STORAGE_CLASS_SINGLE_REPLICA) checks...
        ✔ successful
Ran cluster/ checks...
    Ran ORCHESTRATOR(CLASSIC_FOLDERS) checks...
        ✔ successful
Ran nodes/ checks...
Ran CONTROLPLANECONNECTIVITY checks...
 ✔ 4/4 nodes successful
Ran DNS(FQDN=APPS.<FQDN>) checks...
 ✔ 4/4 nodes successful
Ran DNS(FQDN=INSIGHTS.<FQDN>) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=BA) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=DATASERVICE) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=ORCHESTRATOR) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=PLATFORM) checks...
 ✔ 4/4 nodes successful
Ran OBJECTSTORAGE(PRODUCT=TESTMANAGER) checks...
 ✔ 4/4 nodes successful
Ran REDIS(PORT=6380) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=ASROBOTS, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=AUTOMATIONHUB, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=AUTOMATIONOPS, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=BA, TYPE=ODBC) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=DATASERVICE, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=INSIGHTS, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=NOTIFICATIONSERVICE, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=ORCHESTRATOR, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=PLATFORM, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Ran SQL(PRODUCT=TESTMANAGER, TYPE=ADO) checks...
 ✔ 4/4 nodes successful
Hinweis:
Das oben genannte Beispiel wird gekürzt. Aktuelle Protokolle enthalten weitere Informationen. Wie Sie sehen, wird der Befehl diagnose auf mehreren Ebenen ausgeführt, z. B. Infrastruktur, Netzwerk, Speicher, Pods, DNS usw.

Analysieren der Protokolle

Es gibt zwei potenzielle Probleme, die Sie in den vorherigen Protokollen erkennen können:

  • Istio hat eine falsche Konfiguration, die Probleme beim Zugriff auf die Document Understanding-Plattform verursachen kann:
    ❌ [ISTIO]
    ✔ [ISTIO_SYNC_STATUS] Istio sync is up-to-date
    ❌ [ISTIO_ENVOY_CONFIG_STATUS] Istio Envoy configs are not healthy: Error [IST0101] (VirtualService uipath/du-platform-vs) Referenced host:port not found: "aistorage:5000"❌ [ISTIO]
    ✔ [ISTIO_SYNC_STATUS] Istio sync is up-to-date
    ❌ [ISTIO_ENVOY_CONFIG_STATUS] Istio Envoy configs are not healthy: Error [IST0101] (VirtualService uipath/du-platform-vs) Referenced host:port not found: "aistorage:5000"
  • Data Service ist nicht verfügbar. Siehe Ceph im Codebeispiel.
    ❌ [DATASERVICE]
    ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced
❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-v5krg cannot mount volume: (combined from similar events): Unable to attach or mount volumes: unmounted volumes=[external-storage-creds], unattached volumes=[workload-socket is-secrets openssl istio-podinfo temp-location cert-location istio-data external-storage-creds workload-certs istio-envoy java domain-cert-config edk2 credential-socket tmp additional-ca-cert-config pem istiod-ca-cert istio-token app-secrets ceph-storage-creds]: timed out waiting for the condition
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-xs9t5 cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-taskrunner-787df76c74-98h5l cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found❌ [DATASERVICE]
    ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced
❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-v5krg cannot mount volume: (combined from similar events): Unable to attach or mount volumes: unmounted volumes=[external-storage-creds], unattached volumes=[workload-socket is-secrets openssl istio-podinfo temp-location cert-location istio-data external-storage-creds workload-certs istio-envoy java domain-cert-config edk2 credential-socket tmp additional-ca-cert-config pem istiod-ca-cert istio-token app-secrets ceph-storage-creds]: timed out waiting for the condition
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-runtime-8f5bb7d56-xs9t5 cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found
    ❌ [CANNOT_MOUNT_VOLUME] Pod uipath/dataservice-taskrunner-787df76c74-98h5l cannot mount volume: MountVolume.SetUp failed for volume "external-storage-creds" : secret "dataservice-external-storage-secret" not found

Bekannte Probleme (Known Issues)

Möglicherweise erhalten Sie eine Fehlermeldung ähnlich dem folgenden Beispiel. Sie können dies ignorieren, da keine Actions erforderlich sind.

Zusätzliche Dienstprogramme

Zusätzliche Dienstprogramme

Alle Befehle des Automation Suite -Diagnosetools (check, testund diagnose) unterstützen zusätzliche Filter- und Ausgabeformate.

Filtern

Filter

Beschreibung

Verwendungen

--included

Kommagetrennte Liste der Dienste, die in die Validierung einbezogen werden sollen

/uipathctl health diagnose input.json --versions.json --included ISTIO,INSIGHTS

Dieser Befehl führt die Diagnose nur für Istio und Insights aus.

--excluded

Kommagetrennte Liste der Dienste, die von der Validierung ausgeschlossen werden sollen

/uipathctl health test --excluded ISTIO,INSIGHTS

Dieser Befehl führt den Test im gesamten Cluster mit Ausnahme von Istio und Insights aus.

Ausgabeformat

Das Automation Suite Diagnosetool kann Berichte in mehreren Formaten generieren: json, yaml, textund junit. Sie können diese Werte über das Flag --output an einen beliebigen Befehl übergeben. Diese Ausgabeformate sind praktisch, wenn Sie diese Tools nutzen möchten, um darauf aufbauend Ihr eigenes Framework zur Fehlerbehebung zu erstellen.

Verwendungsbeispiele

Nutzung

Beispielausgabe

./uipathctl health check --included DATASERVICE --output json
./uipathtools health check --included DATASERVICE --output json./uipathctl health check --included DATASERVICE --output json
./uipathtools health check --included DATASERVICE --output json
{ "cluster/": { "DATASERVICE": [ { "name": "DATASERVICE_HEALTH", "description": "Application health check failed: health status is Progressing and sync status is Synced", "status": "failed" } ] } }{ "cluster/": { "DATASERVICE": [ { "name": "DATASERVICE_HEALTH", "description": "Application health check failed: health status is Progressing and sync status is Synced", "status": "failed" } ] } }
./uipathctl health check --included DATASERVICE --output yaml
./uipathtools health check --included DATASERVICE --output yaml./uipathctl health check --included DATASERVICE --output yaml
./uipathtools health check --included DATASERVICE --output yaml
? locationType: cluster : DATASERVICE: - name: DATASERVICE_HEALTH description: 'Application health check failed: health status is Progressing and sync status is Synced' status: failed? locationType: cluster : DATASERVICE: - name: DATASERVICE_HEALTH description: 'Application health check failed: health status is Progressing and sync status is Synced' status: failed
./uipathctl health check --included DATASERVICE --output text
./uipathtools health check --included DATASERVICE --output text./uipathctl health check --included DATASERVICE --output text
./uipathtools health check --included DATASERVICE --output text
Checks run on cluster/ ❌ [DATASERVICE] ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is SyncedChecks run on cluster/ ❌ [DATASERVICE] ❌ [DATASERVICE_HEALTH] Application health check failed: health status is Progressing and sync status is Synced
./uipathctl health check --included DATASERVICE --output junit
./uipathtools health check --included DATASERVICE --output junit./uipathctl health check --included DATASERVICE --output junit
./uipathtools health check --included DATASERVICE --output junit
<testsuite name="Health" tests="1" errors="0" failures="1" time="0" timestamp="2023-06-22T01:59:08.313362+05:30" hostname=""> <testcase name="DATASERVICE_HEALTH" classname="" time="0"> <failure message="Application health check failed: health status is Progressing and sync status is Synced" type=""> </failure> </testcase> </testsuite><testsuite name="Health" tests="1" errors="0" failures="1" time="0" timestamp="2023-06-22T01:59:08.313362+05:30" hostname=""> <testcase name="DATASERVICE_HEALTH" classname="" time="0"> <failure message="Application health check failed: health status is Progressing and sync status is Synced" type=""> </failure> </testcase> </testsuite>

War diese Seite hilfreich?

Support und Services
Hilfe erhalten
UiPath Academy
RPA lernen – Automatisierungskurse
UiPath-Forum
UiPath Community-Forum
Uipath Logo White
Vertrauen und Sicherheit
Nutzungsbedingungen
Datenschutzerklärung
Cookie-Richtlinie
© 2005–2025 UiPath. Alle Rechte vorbehalten