This topic describes troubleshooting steps to be followed if the Dell Telecom Infrastructure Automation Suite migration has failed.
- If the Dell Telecom Infrastructure Automation Suite migration fails, run the migrate command again.
Optionally, you can also run the migrate command along with the force command.
dtias migrate --src-ip <dtiaf-cp1-ip> --bmo-ip <bmo-cp1-ip> --dst-ip <dtias-cp1-ip> --worker-site-map <worker-map-file-path> --force
When you re-run the migrate command, the migrator displays a user prompt for a confirmation. When you run the migrate command along with force command, the migration is initiated immediately without any user prompt.
This command exits the current migration process and initiates a new one. The successfully migrated components will not be affected by this action.
- Open a terminal in the target cluster. Run the following command on the Dell Telecom Infrastructure Automation Suite Global Controller (CP1) node to view the Migrator State Configmap.
kubectl get cm migrator-state-cm -n migrator -o yaml
The Migrator State Configmap displays the migration status of the components in the source clusters that are migrated. The status can be any of the following:
- Pending
- Inprogress
- Completed
- Failed
The following is an example of the expected output format:
apiVersion: v1
data:
BMO_FIRMWARE: Completed
BMO_MEDIA: Completed
BMO_REMOTE_SITES: Completed
BMO_SERVER_TELEMETRY: Completed
BMO_SERVERS: Completed
DTIAF_CFY: Completed
DTIAF_FILES: In Progress
DTIAF_IMGR: Pending
kind: ConfigMap
metadata:
creationTimestamp: "2024-02-10T20:47:19Z"
name: migrator-state-cm
namespace: migrator
resourceVersion: "15026664"
uid: e9e641e9-44b0-4452-84aa-8385191c3ab5