Archive for the ‘vRealize Automation’ Category

Removing stale hosts/cluster compute resource entries from vRA 7

April 1st, 2016 No comments

Update: This did remove all my compute resource configuration within my fabric groups (potentially because I did not create reservations yet which actually utilized these fabric groups and compute resources that I did not want to remove). Please use with caution!

After having finally found the time to set up the latest version of vRealize Automation (7.0.1) and adding my vCenter endpoint everything was looking good, until I got carried away, performed some other tasks, renamed a few clusters in vCenter and then went back to configure my fabric groups.

Too bad that data collection already ran before I renamed the clusters… so as a result I now had stale entries for compute resources when trying to add a new fabric group.


As we can see there is no more cluster called “Lab” in my environment. I tried using a tip from someone else who had seen this in the past and stopped and restarted the agent but that didn’t exactly help.

Read more…

Categories: Homelab, vRealize Automation Tags:

Real life experience on performing a roll back from vRA 6.1 to 6.0.1

March 10th, 2015 No comments

I had to deal with a deployment issue in vRealize Automation yesterday that also included one issue to be the weirdest corner case I have seen so far.

All deployments for any VMs using no vRealize Orchestrator workflow stubs were successful. But let’s be honest, that is pretty boring and doesn’t cover most customers use cases, which means most customers will be using the provided stubs to actually step into the machine life cycle and modify deployment and destruction of VMs using workflows and scripts.

Read more…

vRealize Automation 6.2 stuck indefinitely on additional tenant login

December 27th, 2014 No comments

I had a customer a while ago who was unable to log in into the additional created tenant in vCloud Automation Center 6.0.1. The same issue can be reproduced in vRealize Automation as well. Logins to the default tenant would succeed without any issues and a very similar test environment did work without any issues at all for logins.

Read more…