then the name attribute is completely ignored. This means there's no way to rename a VM on the fly in recompose when the input comes from a vAppTemplate.
Changing this is a feature request.
Note however that if all you do is use recomposeVApp to reconfigure a VM and rename it, then that works. So you can solve your problem by doing 2 recomposes: 1 to instantiate the template, and another 1 to rename the VM.
This error typically is due to the endpoint configuration on the tunnel appliance and ensure it matches what's specified in the URL endpoint. Verify this is setup correctly between the Cloud Replication Manager and the Tunnel appliance.
During the installation of vCloud Availabilty Server at the stage of Lookup service details, we get the error "The IP address of the host could not be determined.". Please help.
com.vmware.vcloud.api.presentation.service.BadRequestException: Unable to delete a resource pool with one or more VMs associated. Evacuate all the VMs before you delete the resource pool.
Checked records in select * from computevm database where computehub_id = 0x42697A0FDBCA497DBAFAC6FAE22E3FF4
There are no entries in the table, id belongs to the desired pool.
API call /api/admin/extension/resourcePool/38c2b6d9-fe0b-4e94-aff3-3f549c697fd7/vmList also returns the absence of a VM in the pool
How can I find out what interferes with the procedure?
VCD's placement engine does *try* to keep items in their current datastore. However, there are many caveats which result in the item being moved. There are also a few known bugs in this area, which have been resolved.
If you could provide logs, as well as information about the request that expands a VM's disk, that'd help us figure out why the disk was moved in your specific case. Depending on whether this is a case we've already encountered, or a new scenario we haven't covered, we can either suggest an upgrade to a build that should resolve your issue, or try to address it in a future release.
[root@osboxes bin]# ./vcd vapp attach vapptest cbam-installer testdisk
vappAttachDisk: Attaching Disk to Virtual Machine cbam-installer(7dbeedf0-d8e2-4467-98d8-2b5bde3c4bf4)
task: 6f395f41-8681-4245-96e1-afbc4d534544, result: error, message: [ 29b5e3a2-dd33-4aec-9317-2cb89c036107 ] Unable to perform this action. Contact your cloud administrator.
Errors:
This is the error message from first attach attempt task.
[ 2ce3f2e7-37ba-4b16-bc40-8ee02d3413bf ] Invalid hard disk parameters specified. The following parameters are invalid or conflict with other configured devices in the virtual machine: [vcId=952a6b3b-2407-4150-b07c-9dff51a28315, moref=vm-816] Adaptor Type: SCSIPARAVIRTUAL, Bus Number: 0, Unit Number: 0
The three following attempts all failed with Internal Server Error on the task with the below error message on the event.
in Azure AD you create a custom enterprise application based on SAML
- you configure which users are allowed to use this method in here (as well on vCloud Director in Administration > Users)
This has to be an emailformat
- you configure SAML: Exchange the vCD Federation Metadata with Azure AD and Exchange the metadata of Azure AD (through the URL, not the downloadable XML) with vCD
- you also configure it to use SHA1 up until vCD 9.5.0.3 and as of vCD 9.5.0.4 you can use the standard SHA256
- vCloud Director supports only tokens with the age of 2hours. if you use AzureAD as the federation IDP you need to downsize the lifetime of the token (being 90days) to 2hrs. this can be done through the Azure AD Policy cmdlet.
the SAML attribute in AzureAD user.useruniqueidentifier is also known as the NameID, this one is the info the vCD is looking for and has to be filled in with either:
- user.mail or
- user.userprincipalname (if you don't have exchange)
sadly i won't have a solution for you but i want attached my understandings of that case because i got the same error and resolved it but not my problem.
Can i assume that you moved all VMs from the old vSphere Cluster to a new one and want to remove this PvDC or its Ressource Pool?
In that case i found out, that if you moved the VMs with vCenter tools and not with vCloud tools you can "empty VM containers".
Or i mean i think this is the basic information of that error. When i move VMs Back to its original place and use "Migrate to.." on each VM in Ressource Pool View (Flash) i solved it.
After every VM was moved with "Migrate to..." i could detach the old Ressourcepool or delete the PvDC.
Sadly the prerequisites to click on 'Migrate to' are not public and i cannot do this.
I found a blog in the internet with the same error and you have to clean up the Database with the "stranded/stale" database entries of old or lost VMs.
After cleaning up this should work again.
At the moment i am searching the official documentation of "Merging PvDCs".
Not the vCloud documentation like "look here you can click on Merge".
Something more like "you have to connect the dvswitches, the datastores must be their, vxlan and vtep must be the same...." documentation....
Hoped my information helped you a bit or you can get more precised?
I'm using vcloud director for the first time. We have a requirement to move the on-prem VM's to AWS. When I create a snapshot for one of the VM which is 8gb in vcloud. I see multiple files in the datastores.
So, I consider a flat.vmdk which was the size of the VM(wild guess) 8gb. When I imported it in AWS and tried to convert it into AMI. It failed apparently "StatusMessage": "ClientError: Disk validation failed [Unsupported specified file format]","
