Jump to content


Photo

XD on AWS volumworker not creating

Started by Todd Dunwoodie , 22 October 2015 - 03:00 PM
4 replies to this topic

Best Answer Paul Howard , 22 October 2015 - 03:47 PM

Hi, Todd.

 

If this is a fresh new XD 7.6 installation in a new VPC, have you installed the controller hotfixes? From this description, the process sounds like it is failing at exactly the point it would fail due to the known issue in 7.6 that was fixed by Controller Update 1 (http://support.citrix.com/article/CTX141735), although I think that is now superseded by Update 2 (http://support.citrix.com/article/CTX142439).

 

If the relevant updates have already been applied to this site, then a scout trace would be the next step.

 

Thanks,

Paul.

Todd Dunwoodie Members

Todd Dunwoodie
  • 15 posts

Posted 22 October 2015 - 03:00 PM

I have created a new XenDesktop 7.6 site in a new VPC and am trying to stand up new catalogs.  The process is failing.  It never spins up the Citrix.Volumeworker Instance.

It creates the Preparation VM and the XenDesktop Temp Instance.  It also creates a VolumeWorker AMI.  But never creates the VolumeWorker Instance in the New VPC.

 

If I create a Catalog in the old site in the previous VPC it works.  I have compared the VolumeWorker AMI and they appear the same.  The both have the tag 

XdConfig
 
XdProvisioned=true
 

and have the same owner etc.

 

I have edited the AWS security group rules to allow All traffic between the DDC Security Group and the VDI security group.

 

The error I am receiving in Studio on the failed catalog creation is 

 

any ideas?  I am getting ready to capture scout logs as the next step.

 

Task Information:

Start Date: Thursday, October 22, 2015

Start Time: 9:12 AM

Finish Date: Thursday, October 22, 2015

Finish Time: 9:25 AM

State: Failed

Master image: XDHyp:\HostingUnits\XXXXXXX.template

Requested machine count: 10

AD account action: Create accounts

Successful accounts: 0

Successful machines: 0

 

Terminating 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.

Stack Trace:

   at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.CheckForTerminatingError(SdkProvisioningSchemeAction sdkProvisioningSchemeAction)

   at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.WaitForProvisioningSchemeActionCompletion(Guid taskId, Action`1 actionResultsObtained)

   at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.StartProvisioningAction()

   at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.RunTask()

   at Citrix.Console.PowerShellSdk.BackgroundTaskService.BackgroundTask.Task.Run()

 

DesktopStudio_ErrorId : UnknownError

ErrorCategory : NotSpecified

ErrorID : NoDiskContentTransferService

TaskErrorInformation : Terminated

InternalErrorMessage : No facility available for disk upload.

This e-mail and its attachments are confidential and solely for the intended addressee(s). Do not share or use them without Common Securitization Solutions’ approval. If received in error, contact the sender and delete them. 

 

 

 



Paul Howard Citrix Employees

Paul Howard
  • 66 posts

Posted 22 October 2015 - 03:47 PM

Hi, Todd.

 

If this is a fresh new XD 7.6 installation in a new VPC, have you installed the controller hotfixes? From this description, the process sounds like it is failing at exactly the point it would fail due to the known issue in 7.6 that was fixed by Controller Update 1 (http://support.citrix.com/article/CTX141735), although I think that is now superseded by Update 2 (http://support.citrix.com/article/CTX142439).

 

If the relevant updates have already been applied to this site, then a scout trace would be the next step.

 

Thanks,

Paul.


Best Answer

Todd Dunwoodie Members

Todd Dunwoodie
  • 15 posts

Posted 27 October 2015 - 03:11 PM

Thanks Paul, the hotfix worked, one more quick question.  I see there are 67 Citrix.XenDesktop.VolumeWorker AMI's going all the way back to March.  

 

Can these be deleted?



arun kumar Members

arun kumar
  • 6 posts

Posted 07 November 2016 - 04:09 AM

Citrix Xen Desktop 7.9 on AWS , Getting  Error 

 

    DesktopStudio_ErrorId : ProvisioningTaskError
    ErrorCategory : NotSpecified
    ErrorID : NoDiskContentTransferService
    TaskErrorInformation : Terminated
    InternalErrorMessage : No facility available for disk upload. No facility available for disk upload. Unable to create any functioning volume service VMs.
    DesktopStudio_PowerShellHistory : Create Machine Catalog 'Citrix MCS Test'
 
Security group allow inboud all traffic and Outboud all traffic 
 
The Xen Desktop Temp machine stops at the following and thows the error message
 
Syncronizing Time Server  : Failed 
Connecting to s3.amazonaws.com : 443 


Ryan Deschaine Members

Ryan Deschaine
  • 5 posts

Posted 16 February 2017 - 08:06 PM

Has anyone come up for a fix for this?

 

Below is what we have already tried

 

Installed Delivery Controller, and configured the MCS connections while installing.

 

Created the API/Key with the following permissions per Citrix article:

IAM User Permissions for AWS using Citrix MCS
----------------------------------------------
{
  "Statement": [
    {
      "Action": [
        "ec2:AttachVolume",
        "ec2:AuthorizeSecurityGroupEgress",
        "ec2:AuthorizeSecurityGroupIngress",
        "ec2:CreateImage",
        "ec2:CreateNetworkInterface",
        "ec2:CreateSecurityGroup",
        "ec2:CreateTags",
        "ec2:CreateVolume",
        "ec2:DeleteNetworkInterface",
        "ec2:DeleteSecurityGroup",
        "ec2:DeleteSnapshot",
        "ec2:DeleteVolume",
        "ec2:DeregisterImage",
        "ec2:DescribeAccountAttributes",
        "ec2:DescribeAvailabilityZones",
        "ec2:DescribeImages",
        "ec2:DescribeInstances",
        "ec2:DescribeNetworkInterfaces",
        "ec2:DescribeRegions",
        "ec2:DescribeSecurityGroups",
        "ec2:DescribeSubnets",
        "ec2:DescribeVolumes",
        "ec2:DescribeVpcs",
        "ec2:DetachVolume",
        "ec2:RebootInstances",
        "ec2:RevokeSecurityGroupEgress",
        "ec2:RevokeSecurityGroupIngress",
        "ec2:RunInstances",
        "ec2:StartInstances",
        "ec2:StopInstances",
        "ec2:TerminateInstances"
      ],
      "Effect": "Allow",
      "Resource": "*"
    },
    {
      "Action": [
        "s3:CreateBucket",
        "s3:DeleteBucket",
        "s3:DeleteObject",
        "s3:GetObject",
        "s3:PutObject"
      ],
      "Effect": "Allow",
      "Resource": "*"
    }
  ]
}
 
Install VDA and shudown the AMI.
 
Created Image as Magnetic per Citrix whitepaper
 
Created Hosting connection inside of Citrix Studio
Connected the Resources to the correct pool in AWS
From the AWS Console we can see the "CitrixTemp" AVD being created, but than terminates after 30-40 minutes 
 

 

Is there a way to recreate the default VPC without involving Amazon in the process?

Perhaps this is the resolution?

 

Hopefully we can help each other here.