Machine catalog updates failure with error the master VM as an invalid configuration
Article ID: CTX495710
Updated On:
Description
VMWARE Hypervisor
When updating a particular machine catalog with a new master image, the operation fails early on with one of the following:
- "action name: updatemachinecatalogprovisiningscheme"
- "action name: MC_UpdateMachineCatalog"
Same issue happens when attempting to rollback to a previous snapshot of same master.
Issue not affecting other catalogs with other master images.
No problems detected performing a Machine Catalog Test or a Hosting test.
- Affected Catalog usually has a very long name, as well as using VMs, Snapshots or VMDK files with very long names.
- As a workaround, updates appear to work when the affected Catalog is empty (eg. has no VDAs).
Resolution
Problem Cause
CDF traces indicate the following:
14:39:23.72441,10408,2300,1,RemoteHCLServerLog,,,,1,Error,"ConsolidateDiskFromVmSnapshot:GetVMDisk error 'PluginUtilities.Exceptions.ManagedMachineGeneralException: Warning, maximum image string length exceeded:
Which indicates that the naming convention used for Machine Catalog, VM and disk files were over the maximum character limit supported by hypervisor.
Long naming conventions for Catalogs, VMs or Disk images may cause Machine Catalog updates to fail using VMWARE hypervisor.
The total Disk Image string length (Product code / Database) is limited to 256 characters.
Example:
Version=2,LsiLogicScsi,1000,group-v1234,[Object Name from Vcenter] Name_of_the_machine_catalog-baseDisk-datastore-1234/Name_of_the_machine_catalog-baseDisk-datastore-1234_11.vmdk,resgroup-123456,Vmfs
Issue/Introduction
