Description of problem:
When we perform a migration and it fails due to some reason, (either an existing DVM bug OR intentionally failing it by providing an invalid cluster_subdomain value inside the controller config) , the rollback of that migration also gets failed at RollbackLiveMigration step, while there are no VMs

Version-Release number of selected component (if applicable):
MTC 1.8.4

How reproducible:
Always

Steps to Reproduce:
1.Deploy an application to migrate in the source cluster
2. Edit the migration controller configuration and set cluster_subdomain to abc.com
3. Execute cutover migration, and wait for the migration to fail.
4. Now perform rollback of the migration.

Actual results:

Rollback also gets failed at RollbackLiveMigration step, while there are no VMs

Expected results:

Rollback should complete successfully.