Tech-Gen

  Non Admins are unable to run 2nd Day Actions outside of the Deployment View with 404 NOT_FOUND error in Aria Automation version 8.17 Issue/Introduction Non administrator users cannot execute day 2 actions outside of the deployment views in Aria Automation version 8.17 The request submission fails with a 404 NOT_FOUND error: 404 NOT_FOUND "Failed to validate form source due to: "; nested exception is org.springframework.web.server.ResponseStatusException: 404 NOT_FOUND   Environment Aria Automation 8.17 Aria Automation 8.18.0 Cause When day2 action call is made from the machines DataGrid, the parameter deployment ID provided is empty due to which request fails to retrieve actions and throws 404 error. Resolution A resolution is scheduled for release with Aria Automation 8.18.1 Workaround:  Users are requested to request the day 2 actions directly from deployment page in the UI OR go to  Service Broker ->  Deployments.

  Error Code: LCMVRAVACONFIG90030 VMware Aria Automation VA Upgrade Status Check failed. Issue/Introduction Applying the vRealize Aria Automation security patch fails using LCM. In order to apply  the patch, customer follows the KB https://knowledge.broadcom.com/external/article?articleNumber=325790 LCM request comes back with the error Code:  LCMVRAVACONFIG90030 VMware Aria Automation VA Upgrade Status Check failed. LCM error details, you can find it in the ar/log/vrlcm/vmware_vrlcm.log 2024-08-28 11:28:58.986 ERROR [pool-3-thread-29] c.v.v.l.p.c.v.t.VraVaUpgradeStatusCheckTask -  -- Un-expected status seen after Upgrade on VMware Aria Automation VA vraNodeFqdn. To know more about the failure, run command "vracli upgrade status --details" on the VMware Ari a Automation VA vraNodeFqdn. Upgrade is not successful, VMware Aria Automation appliance has been auto reverted to its previous working state. You can retry the upgrade by going to the product section 2024-08-28 1...

  Manually unregister an onboarded machine from a deployment in case of an unregister action failure Issue/Introduction Machines fail to unregister and cannot be onboarded again. This article provides information on how to put these machines back to  Discovered  state. Symptoms: After performing the unregister action on an onboarded machine, the machine remains in "onboarded" state in the resource view and cannot be added to a new onboarding plan. Environment VMware Aria Automation 8.x VMware vRealize Automation 8.9.x VMware vRealize Automation 8.10.x VMware vRealize Automation 8.x VMware vRealize Automation 8.7.x VMware vRealize Automation 8.8.x Cause Temporary issues can interfere with the unregistering process. Also, if onboarding isn't completed properly, the machine might not have the required information for unregister to work. Resolution VMware is aware of this issue. Currently there is no resolution. Workaround: To workaround this issue, manually remove the stale ...

  IdP Misconfiguration Causing vIDM Login Failures with OAuth2 "The error message displayed is: https://load-balancer/hc/error." Issue/Introduction This article addresses intermittent login failures encountered by users in a vIDM  environment utilizing OAuth2 authentication with a load balancer.  Environment VMware Identity Manager 3.3.7  Cause The intermittent login failures likely stem from a mismatch between the Vidm Connector hostname configured in the Identity Provider (IdP) and the actual hostname used by the load balancer. Resolution Scenario 1: Single Connector, VIP Address: Update IdP Configuration: Ensure the vIDM Connector hostname (e.g., myconnector.mycompany.com) is configured in the IdP for OAuth2 client settings, not the load balancer hostname (e.g., mylb.mycompany.com). The IdP was configured with the VIP address of the load balancer instead of the individual vIDM Connector hostname. This can lead to login failures if the user is directed to a vIDM Co...

  How to Increase vIDM appliance disk space Issue/Introduction This resource provides instructions on how to increase the disk size of all VMware Identity Manager (vIDM) nodes. Symptoms: After a series of upgrades, the VMware Identity Manager (vIDM) appliances may not have the correct disk size for the updated version. Resolution What is generally observed is when the vIDM appliance has been updated several times, it still features the disk layout from the initial non-Photon installation: The Photon versions features disk space pictured below: To increase the disk size, please take the following steps: Within vCenter, extend Hard disk 1 to 60GB and Hard disk 2 and 3 to 20GB (if Hard disk 4is present, it can be ignored). NOTE: You cannot change the Hard Disk size if there are current snapshots. Take snapshots after the next step. 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 ec...

  Blueprint with ID ...-...-...-...-... not found Issue/Introduction Symptoms: Opening a Deployment in Service Broker shows a Red Banner Deployment details are not displayed and the right panel stays on "Loading..." The deployment can be managed in the Deployments overview, using the Dropdown arrows The user trying to open the deployment has the following roles assigned: "Service Broker User" and "Assembler User" A user which is only configured for "Service Broker User" does not experience this issue The Cloud Template was created in a different Project then as it was deployed from, the Cloud Template is configured as a shared template  Example screenshot: Environment Aria Automation 8.17, Aria Automation 8.18.0 Resolution VMware is aware of the issue and currently investigating.  Possible workarounds are: Add the Account/Group impacted as a Project Viewer of the Project where the shared Cloud Template was created from When removing the role ...

  IP Allocation failure during onboarding Issue/Introduction Symptoms: When Onboarding a virtual machine, the IP Address allocation phase is skipped When attempting to deploy a new VM from vRA, an IP conflict occurs with a previous onboarded VM Environment VMware vRealize Automation 8.x Cause IP conflict occurs because the onboarded VM's IP address was not allocated within vRA. Resolution VMware is aware of this issue. In order to avoid IP conflicts in vRA, follow the steps below before onboarding VMs. Important:  The Prerequisites before onboarding are required even when there are no IP conflicts in the environment. Workaround: Note : To query for allocated IP Addresses, run the following API query https:// vRAFQDN /provisioning/uerp/resources/ip-addresses?expand=true&$filter=(ipAddress eq ' IPADDRESS ') and (ipAddressStatus eq 'ALLOCATED') Where  IPADDRESS  is italicized and is required to be updated with the IP Address you wish to check for. New provisioned V...