WeCloud

Usually, when dealing with a 3-node cluster, it doesn’t matter which node is the master one. In such cases reboot of the appliances should happen always one by one with making sure each appliance has fully loaded before initiating the next reboot. One should make sure there are always 2 (two) running appliances. This ensures quorum is met and environment is fully operational. There are three main scenarios when doing a reboot of vRA: Reboot only the master appliance Make the replication Async. Initiate reboot on the master node. Wait for the appliance to fully load up. Make the replication Sync again.  Reboot any of the secondary appliances Reboot the passive appliance. The potential appliance now becomes passive. Wait for the rebooted appliance to fully load up. The once passive appliance now becomes a potential one. Reboot the currently passive one. Once it’s rebooted it will be automatically switched to the potential role and all roles should remain the same Reboot all three appliances Turn the r…

Error seen in the logs :

2019-01-21 11:07:24,468 | WARN | pool-jetty-375118 | BatchTask | Error executing backend call. | requestId=162e9773-8e5c-4499-a00d-747c
4fd49bbd,request=POST https://clientportal.cloud.com/cloud/amfsecure,requestTime=1548049030064,remoteAddress=172.16.112.50:30049,userAgent=Mozilla/5.0 (Windows NT 10.0
; Win64; x64) AppleWebKit/537.36 ...,accept=*/* method=networkService.createOrgVdcNetwork
org.hibernate.PropertyValueException: not-null property references a null or transient value: com.vmware.vcloud.common.model.net.LogicalNetworkModel.ipScope
at org.hibernate.engine.Nullability.checkNullability(Nullability.java:95)
at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:292)
at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:151)
at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:219)
at org.…

With the new vCloud director releasing and making it full appliance with embedded vpostgres, I though I will put up a post with the complete installation guide. There have been some challenges in the getting the deployment successful.

Prerequisite :
Reverse DNS proxy must be configured for the eth0 ipaddress. This is to get the correct hostname for the appliance. The NFS share is setup for the VCD transfer directory.It is recommended to have the eth0 and eth1 in different subnets. eth0 is for the vcd cell and eth1 is for the vPostgres .The reason for the having 2 subnets is to avoid duplicate entries in the route table. 
Installing vCloud director step by step guide : 






I should ideally be using different submets as per the VMware documentation but since I do not have a different portgroup setup, I am going with the same subnet. As mentioned in the prereq section, the reason for the having 2 subnets is to avoid duplicate entries in the route table


Here we come to the main section. The NTP …

ERROR  :

During a vCloud 8.20 upgrade to 9.5 we got the following error:

Found one or more disabled ESX/ESXi hosts, upgrading will automatically enable all disabled hosts after the upgrade. Do you wish to continue with upgrading the database? [Y/N]  y
The next step in the upgrade process will change the vCloud Director database schema.
Backup your database now using the tools provided by your database vendor.
Enter [Y] after the backup is complete. y
Running 5 upgrade tasks
Executing upgrade task:
Successfully ran upgrade task
Executing upgrade task:
Successfully ran upgrade task
Executing upgrade task:
Successfully ran upgrade task
Executing upgrade task:
.............[13]
Unable to upgrade the database: java.lang.IllegalStateException: Exception encountered while converting the roles


ANALYSIS :

The vcloud-container-debug.log will contain the below entries

2019-03-22 23:24:10,523 | DEBUG    | pool-1-thread-1           | ConvertRoles                   | Loaded 2,865 roles and their rig…

Connect to the vRA appliance using the IP or hostname 




Choose the appropriate setup for your Windows server 


Extract the files to C:\VRMGuestAgent\ . In my case, I have already extracted it. 


Before you install the guest agent download and install the IAAS manager server certificate into the windows machine 



Save the file as Cert.cer 



Install the Cert into the Local machine and Trusted root store



Rename the cert.cer to cert.pem and move it to folder C:\VRMGuestAgent\


Now, copy the certificate file into the vRMGuestAgent Extracted folder 


Open the command prompt as admin and navigate to C:\VRMGuestAgent. In this case 192.168.2.15 is my Manager server . The default port is 443. 


You will see the Guest agent service in the services list. Manually start the service. 




Your windows guest agent is installed :) 

How to Uninstall Guest agent on windows machine 
To uninstall the service 
Stop the VCACGuestAgentService  Run the below command through Command Prompt as Admin   WinService…