Machine Catalog creation on Citrix Cloud to AWS subscription fails with error : A volume service instance could not be launched in your cloud connection. In Studio, select Hosting in the left pane and then select the cloud connection. Click Test Connection in the Actions pane. The test results should provide additional information.

Action Name: MC_CreateMachineCatalogInitialzation
ProvisioningTaskError - ErrorID : NoDiskContentTransferService - TaskErrorInformation : Terminated  InternalErrorMessage : No facility available for disk upload. Unable to create any functioning volume service VMs. No facility for locating manually-bootstrapped volume worker templates on AWS.

Cloud Connector logs show : RemoteHCLServerLog, Error,HypervisorService.GetItemFromPath: No inventory item found with path '/vpc-no_prod-se.virtualprivatecloud/eu-south-1a.availabilityzone/172.22.177.0&**(vpc-076d89d2ac6).network'

1. Master image had an additional 20 GB cache drive. Removing that drive fixed provisioning issue.

---

Problem Cause

'Direct disk upload' to create disk was failing due to,
"PluginUtilities.Exceptions.ManagedMachineGeneralException: Mismatch between VM platform:Windows, and device name:/dev/sdb ---\u003e - CloudCommon.CloudPluginBase.PluginMachineManager.CreateVolumeViaDirectUpload". As this fails, machine creation process had to go through 'Volume Worker' approach.
Note : Direct disk upload eliminates the volume worker requirement for machine catalog provisioning, and instead uses public APIs provided by AWS. 'Direct Disk Upload' Exception points to problem with 'block device mapping' on master image.



 

https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/2203-ltsr/install-configure/install-prepare/aws.html#direct-disk-upload-and-download

https://www.citrix.com/blogs/2019/10/16/troubleshooting-tips-from-the-field-for-machine-creation-services-in-aws/