WeCloud

Symptoms : Unable to see the vApp on the HTML5 UI  The vApp is seen on vCloud director Flex UI  Cause :  -  This happens if the VM was created as a standalone VM from the HTML5 UI.   - Since there has been no improvement done recently on the Flex UI, the old UI does not have a view  to display standalone VMs seperately. Hence the standalone VMs are displayed in the vApp Fix : Run the below statements for the list the vcloud=# select vapp_id from vapp_vm where name like '%stdalone%'; -[ RECORD 1 ]--------------------------------- vapp_id | b1c58135-7c93-43ac-a7d2-c8412fc74c98 vcloud=# select * from vm_container where sg_id = ' b1c58135-7c93-43ac-a7d2-c8412fc74c98 '; -[ RECORD 1 ]-------------+----------------------------------------------------------------------------------- sg_id                     | b1c58135-7c93-43ac-a7d2-c8412fc74c98 name                      | stdalone-04ad56d5-2a60-4a06-a750-f3e371d328

vCloud director does not have an GUI way of exporting the support bundle as of now To collect the vCloud Director support bundle, establish an SSH connection to one of the vCloud Director VMs and run the following command: /opt/vmware/vcloud-director/bin/vmware-vcd-support Above command collects only log bundle for single  cell by default) Usage : vmware-vcd-support [OPTIONS]   -d,       --dbdump           Collects DataBase dump.   -l,       --log              Collects logs on single cell (default)                                or multiple cells (with --multicell)   -a,       --all              Collects all data bundles for single cell.                                If used with --multicell option then it collects                                all data bundles from multiple distributed cells.   -m,       --multicell        If used with --all option, collects all data bundles                                from multiple cells. If used with --log then          

This blog is talks about the way to deploy vCloud director 10.x appliance without zero errors in first attempt.  There are just 3 requirements which is mandatory for error free deployment.  Only prerequisites :  1. Dedicate 2 IP addresses (eth0 & eth1) - Eth0 is for the HTTPS and Console proxy.  Yes, both HTTPS & Console Proxy uses same interface. The console proxy uses a custom port 8443 . - Eth1 is dedicated for postgres database connection only 2. Add DNS entries for the IP addresses (Forward and Reverse DNS lookup) - Reverse DNS lookup entry is a must - If you have noticed vCD appliance taking PhotosOS as the hostname , it is because the reverse DNS entry does not exist. 3. Prepare the NFS server i. Create a NFS folder with full read & write permissions. ii. The format to use is   NFS_Server_name :/ Directory_name (ex : nfs.wecloud.lab :/vCD97rpr )  iii. Make sure the directory contains no old deployment entries. Its better clean

Issue :  Adding vCenter instance to vRO completes but the inventory has below messages. https://vcenter.wecloud.lab:443/sdk (unusable: java.lang.ClassCastException: com.vmware.vcac.authentication.http.spring.oauth2.OAuthToken cannot be cast to com.vmware.vim.sso.client.SamlToken) Storage Policies (unusable: PBM error: java.lang.RuntimeException: java.lang.ClassCastException: com.vmware.vcac.authentication.http.spring.oauth2.OAuthToken cannot be cast to com.vmware.vim.sso.client.SamlToken) Storage Policy Components (unusable: PBM error: java.lang.RuntimeException: java.lang.ClassCastException: com.vmware.vcac.authentication.http.spring.oauth2.OAuthToken cannot be cast to com.vmware.vim.sso.client.SamlToken) Resolution :  Add the vCenter instance as Share a unique session Hope it helps :)