Hello,
I have just upgraded a lab from vCloud Director 9.0.0.2 to vCloud Director 9.0 and have an issue with the tenant portal not loading correctly and displaying "No Datacenters are available". This is affecting all Orgs. I have had a quick look with Fiddler and I can see the API calls to /api/query?type=orgVdc and can see the XML responses with the OrgVDC data however the UI just displays "No Datacenters are available".
Is anyone aware of a solution to this issue ?
I had the same issue using internal minted certs, this fixed it with the help of VMware Support
Try this get your public keys in a base64 format in the PUBLIC API URL section in vCloud Director, in my case it was someting like this, internal 2 tier CA:
-----BEGIN CERTIFICATE-----
ROOTCA KEY
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
ISSUING CA KEY
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
HTTPS LEAF KEY
-----END CERTIFICATE-----
I don't completely understand the question, I mean: users are not saved locally on the cell, they're in the database.
If you need the users on a second cell in production, it will suffice to join the cell because the user base is the same, if you need to build a test environment, you should clone both the cell and the database server.
Best regards, e.
Thank you for the info; a quick fix in the end; hopefully they will publish a KB shortly. I have written up a quick procedure for anyone with this issue here: http://vexpert.me/17M
Anyone have troubles uploading ISO's in the latest tenant UI? After hitting OK on the Upload Media dialog, we're getting a [object Object] error. Reproduces in Safari, Firefox, and IE11.
Hi there,
I have a bunch of vms inside vapps with a nic driver e1000 we would like to change that to vmxnet3 without adding a new nic since this will change the mac address and we need to keep the same due to software license.
Vcloud GUI doesn't allow me to do this change I was wondering if its possible to do this through the rest api so far I've managed to extract the xml where the nic definition is
but when I'm trying to put the xml back with the driver I want I'm receiving a "Forbidden" message.
Regards
I like this community... The only help that i found is by myself !
So, following my issue i've tried some actions and the only that works is :
- Shutdown the VM
- Unregister the VM
- Register the VM out of the vCloud Organization
vCloud doesn't retry to inventor the VM and don't create directory each time he try.
I hope that will be helpfull for any people facing the same issue.
Regards
Hi there Cronistar,
I have had this issue (unfriendly error) when attempting to upload an ISO via the Tenant Portal with an identical name to a Catalogue; is this the case for you also or is this just being thrown whenever you attempt an upload ?
Why don't you:
- Update VCD to 9.x
- Update vCenter to 6.5
- Create a new cluster with 6.5 ESXI hosts on new hardware
- Add the new cluster as 2nd Provider VDC in vCloud
- Migrate the tenants
- Decommision old hardware Provider VDC
Best regards, e.
Hi Cronistar and thank for the feedback. We are working on a fix for displaying proper error message.
In addition to the scenario which Adrian Begg described above, this error message might also be seen if did not select a catalog within the “Upload Media” modal or if you have no permissions for uploading media to the specified catalog.
-Radostin
Hi there,
I have a newly deployed vCloud Director 9.1. All seems to be fine, but I cannot enter into the console with FQDN (like https://vcloud.mycompany.local) but works ok using the IP (https://10.1.0.100).
Could someone point me in the right direction?
Thanks a lot
1) Can you check VCD cell etc/resolv.conf file to confirm DNS is configured correctly ?
2) Do check if forward and reverse lookup is configured in DNS for VCD IP's (Usually people skip reverse zone entry)
3) If everything is fine, do a nslookup within VCD both via IP&FQDN and let me know the results.
I've finally found the problem. It was the "Administration / Public Addresses".
Now I can use the FQDN to log in the console but a new problem appears. Using the console with the IP, I've created a tenant with resources, log in as the tenant and deployed two virtual machines. Now, entering with FQDN, the console shows a message saying "There is no Datacenter".
I don't know if this can be fixed or I need to delete all tenants created using IP and recreate them using FQDN.
D.
That ended up being our issue- permissions. Even though the I had access to the catalog, I couldn't upload an ISO unless I had Org Admin permissions.
Has anyone tested the Cloudify vCloud plugin? I'm having a hard time getting this to work as there is no compiled vCloud module available on the Cloudify plugin site: https://cloudify.co/plugins
Hi maal11! You might want to consider upgrading to the vCD version 9.1. This version allows you to upload both OVA/OVF and other media files without any plugins by using the new HTML5 tenant portal. Previous versions relied on a client integration plugin (CIEP). I've had some issues getting a working combination of CIEP and suitable webbrowser in the past. So I can see how this would give you problems as well.
Hi mahmoud,
You might also want to try what is described in this VMware Knowledge Base article and in greater detail in this blog: vCloud Director Client Integration Plugin is not working .
-Radostin
hi,
do we know if this causes any issues in terms of VM availability? If we have an existing org vdc using the storage profile?
Hello Everyone
I'm evaluating vDirector and i need help to understand how to make new vms in a tenant to automatic connect to a default network.
I have a default system tenant with a global catalog with Windows 2016. When i deploy that template in a Tenant, i need to edit the virtual machine and select the network.
Is there a way to make all new virtual machines for that tenant or all tenants to use an Edge network by default?
Thanks!
I have been able to repro this to with ESXi 6.5 & VCD 8.20.1. The easy fix is to just 'reconnect' the vCenter Server in VCD. It will then do a full inventory and display the correct resource pool settings.