If an HCX Bulk Migration group has a large number of Virtual Machines (the amount depends upon your environment), then the Bulk Migration may or may not fail HCX Validation before migration. The migration may show the base sync progress stuck for a Virtual Machine in the migration group if it does pass HCX Validation.
The validation error in the HCX UI may present as "Validation couldn't be performed at the peer. Reason: Read timed out"
HCX Cloud side web logs may have the error "Unable to find a Service Mesh for the given service: [BULK_MIGRATION], source and destination placement Details:"
Please note these errors may be caused by other reasons as well.
Known versions impacted: HCX 4.8 or HCX 4.9.
Migration Group with a large number of Virtual Machines and the Service Mesh is selected in the migration options.
If the Service Mesh is selected as an option when creating a HCX migration group of Virtual Machines, then validating or starting the migration will check the Service Mesh details for each Virtual Machine in the migration group. With a large number of Virtual Machines in a migration group, this can cause a timeout.
This will be permanently resolved in HCX version 4.10.
Workaround:
Recreate the migration group of Virtual Machines, but do not specify the Service Mesh in the Interconnect Options, leave it with "(Optional: Service Mesh)"
as shown below.