Tech-Gen

  VRA API Authentication: Ensuring Secure Access and Understanding Authentication Methods NOTE: Get Your Access Token for the VMware Aria Automation API Note: The API token is valid for 90 days and can be used to generate a new access token when the access token expires. You cannot revoke the refresh token. IaaS API to request the access token (bearer token): Note: After 25 minutes of inactivity, the access token times out, and you must request it again. You may revoke an access token at any time. Using APIs is an effective way to programmatically access vRealize Automation (vRA). However, secure access to your API is essential when managing and automating your infrastructure. This article explores VRA API authentication using API tokens, a secure and efficient way to programmatically access vRA resources. Understanding vRealize Automation VMware vRealize Automation is a robust cloud management platform that empowers orga nizations to automate and orchestrate the provisioning and m...

  Extend HardDisks/Partitions on the vIDM Appliance Our vIDM appliance is now at 3.3.4, was updated several times and still has the disk layout from the initial 3.3.2 installation: The pre check to 3.3.5 now fails complaining: Disk space on /opt/vmware/horizon should be at least 7 GB for upgrade bundle upload. Current available space on /opt/vmware/horizon is 2 GB in node. So i decided to extend the disks and partitions to match the 3.3.5 vIDM disk settings: The steps are quite simple and can be done online: Extend Hard disk 1 to 60GB and Hard disk 2 and 3 to 20GB in vCenter (Hard disk 4 can be ignored) After that is a good time to take a snapshot of the VM. Login as "root" to your appliance let linux rescan for the disk changes:   echo 1 > /sys/class/block/sda/device/rescan echo 1 > /sys/class/block/sdb/device/rescan echo 1 > /sys/class/block/sdc/device/rescan   Check if the new disk sizes are recognized with dmesg:   dmesg -T | grep "detected capacity...

  vIDM upgrade stuck at "Waiting for SaaS to come up on the VMware Identity Manager Host" We started the upgrade from our vIDM installation from 3.3.4 to 3.3.5 in vRLCM but it hangs at "Waiting for SaaS to come up on the VMware Identity Manager Host". Looking at the IDM system diagnostic page turns out that the "ACS Health - Application Deployment Status" service was in error state. The log file for this service is found at /opt/vmware/horizon/workspace/logs/accesscontrol-service.log and there was the error: ERROR your.idm.appliance.com:accesscontrol (localhost-startStop-5) [;;;] org.springframework.boot.SpringApplication - Application run failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [com/vmware/vidm/accesscontrol/db/DbDataStoreAutoConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire...

  Aria Automation upgrade to 8.14 fails with error "LCMVRAVACONFIG90029" Deploying project services. Symptoms Aria Automation upgrade to 8.14 fails with error " LCMVRAVACONFIG90029 " Deploying project services The upgrade failed while deploying the services we can see the  project service app  in Error and crash loop [INFO][2023-11-15 06:19:23][XXXXXXXXXXXX.vmware.cba] Synced upgrade data with node: xxxxxxxxxx.vmware.cba [INFO][2023-11-15 06:19:24][ xxxxxxxxxx.vmware.cba ] Deployment of infrastructure and application services started. [WARNING][2023-11-15 07:22:27][ xxxxxxxxxx.vmware.cba ][Exit Code: 123] Error while deploying infrastructure and application services. [INFO][2023-11-15 07:22:27][ xxxxxxxxxx.vmware.cba ] Shutting down application services... Cause The problem causing the failure are duplicated database entries in project-db. Impact / Risks Upgrades to 8.14 onwards will fail. Resolution This is a known issue and likely to be made availabl...

  VMware Aria Automation New Features in versions 8.11.2, 8.11.1 8.11.0 and 8.10.2 The latest release is 8.11.2 released in March 2023 VMware is enhancing the Aria Automation the Multicloud Management solution has a very frequent release cycles to add new features to enhance the product and meet customer demands. Here is the glance of the latest features released in recent versions of VMware Aria Automation. The table format of the latest features comes handy, I am keeping latest four versions this will be very helpful in understanding that what is newly available. I have planned to maintain this way to have reference to few latest versions as some of you are running previous versions and can easily reference when needed. This time there are 5 new features have been added related to  API, Azure, Saltstack and Cloud Extensibility Proxy.

  VMware Aria Automation New Features in versions 8.13.1, 8.13 and 8.12.2 The latest release is 8.13.1 released in September 2023 VMware is enhancing the Aria Automation the Multi-Cloud Management solution has a very frequent release cycle to add new features to enhance the product and meet customer demands. Here is a glance at the latest features released in recent versions of VMware Aria Automation. The table format of the latest features comes in handy, I am keeping the latest three versions which will be very helpful in understanding what is newly available. I have planned to maintain this way to have reference to a few latest versions as some of you are running previous versions and can easily reference when needed.

  VMware Aria Automation (Formerly known as vRealize Automation) fixing the error status code 500 when Content source with ABX is created and action has its "shared" field with a NULL value. Symptoms VMware Aria Automation Service Broker has а content source of Type " Extensibility actions " for a certain project which contains actions, but the " Number of items " show that fewer actions are synced than the total number.  For example, 5/10 will be shown, and a red exclamation mark next to it. This means that not all actions are synced in the content source and the problematic ones will not be available for use in the Catalog. Cause A change has been introduced in early versions of VMware Aria Automation (around 8.2, or even earlier) for which actions created before that version will not be possible to be used as a content source. This is due to a bug introduced in that version. Older actions, which are created before the bug was introduced will not be acce...