DMS Known Limitations

The following are the known DMS limitations:

• The current DMS support does not support running the DMS Ansible installation from the same server allocated for the DMS service. Ansible should be run from a separate machine than the DMS server.

• Thick clone progress reporting granularity might be somewhat coarse at times. Progress may increment in large jumps. Progress may also increment to 100% before the workflow has completed.

• dms.env is not parsed correctly. On some container shells, the playbook fails while converting dms.env into Ansible variables, and the error is hidden by no_log. As a workaround, contact Lightbits Support for a patched playbook.

• Observability play fails with "image_registry is undefined". As a workaround, define image_registry in inventory/group_vars/all.yml, as shown in the installation procedure.