HCX - OSAM Failed to prepare parameters for creating VM "JSONArray not found"
Article ID: 321607
Updated On:
Products
VMware HCX
Issue/Introduction
Identify and remediate a known issue with HCX OSAM migration workflow.
Symptoms:
During migration of a VM using OSAM (OS Assisted Migration), it may fail to instantiate the VM on the cloud and we can see following error:
2021-05-02 01:32:45.921 UTC [OsAssistedMigrationService_SvcThread-342, Ent: HybridityAdmin, , TxId: ########-####-####-####-########8f2b] ERROR c.v.v.h.m.common.MigrationJobHelper- Subflow Exception stack trace is : java.util.concurrent.TimeoutException: Failed to prepare parameters for creating VM in 300000 ms - JSONArray[3] not found.
Location of App Engine log:
- HCX Manager : /common/log/admin/app.log
Cause
In OSAM workflow, we use sentinel agent software which can be installed in source Linux/Windows system running on a Non-vSphere inventory, for example: KVM/Hyper-V.
When we use docker/container services inside those Linux/Windows systems, then sentinel software reports below NICs to HCX manager:
HCX OSAM expects the same number of NICs should be available consistently before and during the migration transfer workflow. Incase any one of container is destroyed during the migration, the vethNNN interface will vanish, which may result in the failure of migration during course of workflow.
IMPORTANT: From the docker public documentation, there is a one-to-one mapping with a docker container to vethNNN interface.
When we use docker/container services inside those Linux/Windows systems, then sentinel software reports below NICs to HCX manager:
- eth0
- docker interface
- bridge interface
- vethNNN
HCX OSAM expects the same number of NICs should be available consistently before and during the migration transfer workflow. Incase any one of container is destroyed during the migration, the vethNNN interface will vanish, which may result in the failure of migration during course of workflow.
IMPORTANT: From the docker public documentation, there is a one-to-one mapping with a docker container to vethNNN interface.
Resolution
None
Workaround:
IMPORTANT: As long as the number of virtual interfaces vethNNN DO NOT change during the course of migration, then it should succeed.
User is suggested to ensure those virtual interfaces vethNNN should no longer vanishes during the whole course of migration.
Alternatively,
User can also disable the docker and subsequent containers before starting the OSAM migration and same can be re-enabled again, once VM gets migrated and instantiated successfully on the cloud/target side.
Workaround:
IMPORTANT: As long as the number of virtual interfaces vethNNN DO NOT change during the course of migration, then it should succeed.
User is suggested to ensure those virtual interfaces vethNNN should no longer vanishes during the whole course of migration.
Alternatively,
User can also disable the docker and subsequent containers before starting the OSAM migration and same can be re-enabled again, once VM gets migrated and instantiated successfully on the cloud/target side.
Additional Information
Impact/Risks:
- It will impact OSAM migration for ANY source machine where docker/container is running.
- There will be NO impact to Network Extension services.
Feedback
Yes
No
Powered by
