Due to create VM behavior change after upgraded ESXI host to vSphere 6.7.
Before vSphere 6.7, the configuration parameters "namespaceMgr.dbFile" is default created under Edit Settings -> VM options -> Advanced
After vSphere 6.7, there is no "namespaceMgr.dbFile" by default settings.
Case 1:
If user migration master image from vSphere 6.5 to vSphere 6.7 need to double checking the namespaceMgr.dbFile be migrated as well.
Case 2:
Rename the master image after created the VDI snapshot. it always got the issue due to namespaceMgr.dbFile inconsistent
here is vmware-0.log from cp-parent-xxx
------------------------------------------------------------------
2019-02-22T12:10:49.797Z| vmx| W115: InstantCloneReplicateFile: Source file path '/vmfs/volumes/5bf6a936-cc4b5753-ceab-0024e842aaff/cp-parent-11820eb1-bff8-4f27-937e-d51613ca77f7/GVM-W10.db' does not exist!
2019-02-22T12:10:49.825Z| vmx| I125: MigrateSetStateFinished: type=2 new state=12
2019-02-22T12:10:49.825Z| vmx| I125: MigrateSetState: Transitioning from state 11 to 12.
2019-02-22T12:10:49.825Z| vmx| I125: Migrate: Caching migration error message list:
2019-02-22T12:10:49.825Z| vmx| I125: [msg.checkpoint.migration.failedReceive] Failed to receive migration.
2019-02-22T12:10:49.826Z| vmx| I125: Migrate: cleaning up migration state.
--------------------------------------------------------------------
Before rename the vmx and vmsn file with namespaceMgr.dbFile => GVM-W10.db
After rename the master image to Win10RS5, the namespaceMgr.dbFile changed to Win10RS5.db on vmx file but vmsn still keep the GVM-W10.db not change.
As the result, the db file not copy to cp-parent-xxx and cause the problem.