Description

During the execution of the VMware to OpenStack migration using the OpenStack Migration Toolkit, the Ansible task TASK [os_migrate.vmware_migration_kit.import_workloads : Create instance] hangs indefinitely when the underlying OpenStack instance creation fails due to a scheduling error (No valid host was found.).

The Ansible playbook fails to properly detect and report the ERROR status of the OpenStack server, leading to a stalled migration process that requires manual intervention to detect and resolve.

Steps to Reproduce

1. Configure and execute a VM migration from a VMware environment to RHOSO using the Red Hat OpenStack VMware Migration toolkit.

1. Ensure that the target OpenStack environment has a constraint (e.g., flavor limits, unavailable compute hosts, insufficient resources) that will prevent the VM from being successfully scheduled.

1. Monitor the execution of the Ansible playbook.

1. The task TASK [os_migrate.vmware_migration_kit.import_workloads : Create instance] will be reached.

Expected Results

1. The Ansible task TASK [os_migrate.vmware_migration_kit.import_workloads : Create instance] should time out, fail, or exit gracefully within a reasonable timeframe (e.g., 10-15 minutes).

1. The task failure message should clearly indicate that the OpenStack instance entered an ERROR state and report the scheduling failure (e.g., "Instance entered ERROR state: No valid host was found.").

Actual Results

1. The Ansible task TASK [os_migrate.vmware_migration_kit.import_workloads : Create instance] hangs/stalls indefinitely.
2. Manual inspection of the OpenStack environment shows the newly created server in an ERROR state.

openstack server list output:

| 1166a8c5-fddf-44e2-a157-1361914b60b2 | winweb01-zcvr9 | ERROR | (...) | N/A (booted from volume) | osm-vmware-winweb01-zcvr9-7454 |
The detailed server fault clearly indicates the scheduling issue:

openstack server show winweb01-zcvr9u fault details:

| fault | {'code': 500, 'created': '2025-10-03T16:41:49Z', 'message': 'No valid host was found. ', 'details': 'Traceback (most recent call last):\n (...) \nnova.exception.NoValidHost: No valid host was found. \n\n'} |

Workaround (if applicable)

The immediate workaround is to manually cancel the running Ansible playbook and then either:Delete the failed instance from OpenStack.Resolve the underlying OpenStack scheduling issue (e.g., increase resources, ensure compute hosts are available).Re-run the migration playbook from the relevant step.