- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
- After Disaster Recovery Dapr is not working properly for Task Mining
- Task Mining initialization issue in Kerberos
Automation Suite on EKS/AKS installation guide
After Disaster Recovery Dapr is not working properly for Task Mining
After a Disaster Recovery, Dapr is not restored properly, and the certificates needed by dapr to provide services for Process Mining and Task Mining are incorrect. The dapr, processmining, and taskmining applications appear to be healthy first, but will then go back to progressing state and the environment becomes unstable. When logging in to Process Mining or Task Mining, the application may not load, or return unexpected errors.
This page describes the steps you should take to resolve the issue.
Overview of the steps
- Delete all dapr secrets and the mutatingwebhookconfiguration.
- Resync all dapr secrets and the mutatingwebhookconfiguration.
- Restart dapr-sentry deployment and wait to the deployment is finished.
- Restart dapr-operator deployment and wait to the deployment is finished.
- Restart dapr-sidecar-injector deployment and wait to the deployment is finished.
A detailed description of the steps is provided next.
Deleting dapr secrets and the mutatingwebhookconfiguration
-
Go to Applications in ArgoCD.
-
Select the dapr application card to open the dapr app details tree.
-
Locate the dapr secrets.
The secrets must be recreated. You can do this by deleting each secret.
-
Open the context menu of the secret and select Delete.
-
In the Delete resource confirmation dialog enter the name of the secret and select OK to confirm.
-
Repeat steps 4 and 5 for the remaining secrets.
-
In the dapr app details tree, locate the mutatingwebhookconfiguration.
Note:You can recognize the mutatingwebhookconfiguration from the label MWC.
-
Open the context menu of the secret and select Delete. In the Delete resource confirmation dialog enter the name of the mutatingwebhookconfiguration and select OK to confirm.
Syncing the dapr secrects and the mutatingwebhookconfiguration
-
Some of the secrets are immediately recreated. This is indicated by a green check mark on the secret card.
If a secret is not recreated, you need to sync to recreate the secret.
-
Locate the secret you want to recreate and select Sync from the context menu.
-
In the pop-up panel, select SYNCHRONIZE.
-
Repeat steps 2 and 3 for all the secrets that you want to recreate.
-
In the dapr app details tree, locate the mutatingwebhookconfiguration.
Note:You can recognize the mutatingwebhookconfiguration from the label MWC.
-
Open the context menu for the mutatingwebhookconfiguration and select Sync.
-
In the pop-up panel, select SYNCHRONIZE.
Restarting the deployment
After you deleted and synchronized the secrets and the mutatingwebhookconfiguration, you need to restart the deployment.
-
In the dapr app details tree, locate the dapr-sentry deploy card.
-
Open the context menu and select Restart.
A confirmation dialog is displayed.
-
Select OK to confirm the restart. The dapr-sentry deployment starts. When the deployment is finished, a green heart appears. Wait for the deployment to be finished.
-
In the dapr app details tree, locate the dapr-operator deploy card.
-
Open the context menu and select Restart.
-
In the confirmation dialog, select OK to confirm the restart. Wait for the deployment to be finished.
-
In the dapr app details tree, locate the dapr- sidecar-injector deploy card.
-
Open the context menu and select Restart.
-
In the confirmation dialog, select OK to confirm the restart. Wait for the deployment to be finished.
Important:Restart the deployments in the described order and make sure a deployment is ready before starting the next deployment.
- dapr-sentry
- dapr-operator
- dapr-sidecar-injector
You can now check that dapr is working correctly by looking at processmining, as previously described. Now there should be 3 containers in the pod and the daprd container should be present in the LOGS.
Task Mining should work properly now.