Tag

The following post describes how to update vRealize Automation from 8.0.x to 8.1 manually. Most of the guides that tackles the topic assumes you are directly connected to the internet to pull the upgrade binaries. Unfortunately, this is not the case on some environments where the solution is deployed in an airgapped setup. With that said, here’s the high-level steps on how to go about bring up the solution to 8

Making a post on this as I experienced this first hand. Issue is, after reboot, some pods will not run. Specifically, vco and pg. This can be verified by executing the following command in one of the node: kubectl get pods –all-namespaces You’ll notice some pods will be CrashLoop state. To resolve, the following KB will help: https://kb.vmware.com/s/article/78235 For new installs: https://kb.vmware.com/s/

When doing an upgrade via LCM of vRA from 8.0 to 8.0.1, you might encounter this error: Disk space on root partition (/) on VM Disk 1 (/dev/sda4) should have atleast 20 GB of free disk space. This is because initial installation of vRA only has small disk not enough for upgrade. The issue is documented in the Known Issue for vRA 8.0.1 here To resolve, WITHOUT POWERING OFF your Virtual Appliance, go to each of the vRA

Recently had a requirement to limit the number of VM requests per submission in vRA 6.2 By default, there are currently no controls in place to limit this value. Checked around in VMware and found a solution: NOTE: Unsupported solution Go to Windows IaaS server Go to the following path: C:\Program Files (x86)\VMware\vCAC\Server\Website\Leases Edit ConfirmNewRequest.aspx Look for trMachineCount element and edit the n

Doing REST API calls via Powershell is straight forward using the Invoke-RestMethod cmdlet. Using the examples from inkysea’s blogpost, I’ll be showing how to do this calls to vRA using Powershell. To start off, we need to define the header and the body payload After which, we define the URI/ vRA URL to pass the REST payload We then invoke the Invoke-RestMethod cmdlet ConvertTo-Json was done in $bo

I recently encountered issue in the installation IaaS component of vRealize Automation 6.2.1. Normally, you just run the pre-req automation PS1 script, execute the IaaS installer and you’re all set. But for this instance, I keep receiving the below error: System.Data.Services.Client.DataServiceTransportException: The underlying connection was closed: An unexpected error occurred on a send. —> System.N

Over the week, I was asked to prepare a POC that uses vRealize Automation to provision AWS workloads. Being a AWS noob, I had to reference few articles to get this going. Here are the steps to help you: Using: vRealize Automation 6.2.1 AWS Sign-up Create an AWS Account. You’ll be needing Credit Card information for this. After the Account Creation – you need to wait a maximum of 24 hours before you can st