Skip to main content

Posts

  Infinite Browser Refresh Loop Triggered by Deployment Filter in Aria Automation 8.18 Issue/Introduction Users are experiencing an issue where applying a deployment filter in Aria Automation 8.18 causes an infinite reload or refresh loop in their browser. This issue persists across various browsers, including Firefox, Edge, and Chrome. The problem manifests when a deleted deployment is opened and then closed, leading to the browser crashing upon subsequent attempts to open other deployments. Environment Aria Automation 8.18 Cause The issue arises due to a defect in the Service Broker component of Aria Automation. When navigating to the deployments list page with a saved filter selection, the system attempts to update the URL with the saved filter state as URL parameters. This behavior causes a conflict when the Service Broker UI is displayed within an iframe. A new navigation router event, triggered by manipulating the iframe's history, disrupts the flow of URL query parameters, l...
Post a Comment
Read more
  Aria Automation Orchestrator shows "Action is using runtime python 3.10 which is not available" Issue/Introduction After upgrading Aria Automation/Orchestrator to version 8.17 deployments show missing runtime environment metadata. Impact: Workflows using Node.js, Python or PowerShell might fail post upgrade or after a restart of Orchestrator. Environment VMware Aria Automation/Orchestrator 8.17 Cause A race condition while loading the images for runtime environments might lead to Orchestrator caching available runtime images before the full loading has completed. Resolution This issue is resolved in versions 8.18.1. Workaround : Restart the orchestrator server Kubernetes container using the following command: kubectl -n prelude get pods -l app=vco-app -o custom-columns=name:metadata.name --no-headers | xargs -I{} kubectl -n prelude exec {} -c vco-server-app -- bash -c "kill 1"
Post a Comment
Read more
  vIDM appliance has no space left on device /db for audit data Issue/Introduction This article provides steps to add space in the vIDM appliance adding config to limit audit data. vIDM appliance /db file system is almost full, for example usage exceeds about 90% and more. You will see these errors: check /db file system usage by df command as follows Filesystem 1M-blocks Used Available Use% Mounted on /dev/mapper/db_vg-db 10076 8318 1246 87% /db Getting vIDM log-bundle fails with the error:  No space left on device. Environment VMware Identity Manager 3.3.x Cause vIDM appliance uses device /db for Elasticsearch, RabbitMQ and internal DB PostgreSQL.  /db    |- data    |- elasticsearch    |- log    |- lost+found    |- temp A large number of audit data for Elasticsearch uses almost all space on device /db file system. As the default settings vIDM appliance keeps audit data forever, the vIDM file system will eventually fill u...
Post a Comment
Read more
  Scheduled workflows fail post upgrade of VMware Aria Automation/VMware Aria Orchestrator to version 8.18 Issue/Introduction Workflows scheduled in the VMware Aria Orchestrator fail after upgrading to VMware Aria Automation/VMware Aria Orchestrator version 8.18. The same workflows run successfully when executed manually (without scheduling). Environment   It affects both Standalone VMware Aria Orchestrator and embedded VMware Aria Orchestrator. Cause The issue is due to regressions in the VMware vCenter (VC) plugin on VMware Aria Automation/VMware Aria Orchestrator 8.18. Resolution This is a known issue with the VMware Aria Automation/VMware Aria Orchestrator 8.18 and the workaround is to update the VC plugin on VMware Aria Orchestrator with the latest version (attached with the KB). Alternatively, wait for the official fix in VMware Aria Automation/VMware Aria Orchestrator 8.18.1. Workaround :               Note: Take (non-memory)  sna...
Post a Comment
Read more
  vRA 8 upgrade preparation fails: "Attempt failed to run command: /opt/scripts/upgrade/ssh-noop.sh" Issue/Introduction Symptoms: vRealize Automation 8.x upgrade fails with the error: Error Code: LCMVRAVACONFIG90029 Preparation for upgrade has discovered problems. Review to error report below to correct the problems and try again. The services remained in working order. vRealize Automation Upgrade Errors: [vra_fqdn][Exit Code: 255] Attempt failed to run command: /opt/scripts/upgrade/ssh-noop.sh. Pseudo-terminal will not be allocated because stdin is not a terminal. Welcome to VMware vRealize Automation Appliance 8.9.1 root@vra_fqdn: Permission denied (publickey,password). [vra_fqdn] Remote command failed: /opt/scripts/upgrade/ssh-noop.sh at host: vra_fqdn [vra_fqdn] Remote command failed: /opt/scripts/upgrade/ssh-noop.sh at one or more nodes Environment VMware vRealize Automation 8.x Cause This issue can be caused by a corrupt  /root/home/.ssh/authorized_keys  file. Resol...
Post a Comment
Read more
  vRealize Automation 8.x upgrade failed when iptables.service did not start Issue/Introduction To be able to successfully upgrade the vRA cluster. Symptoms: The upgrade process appeared to complete successfully on two of three nodes. kubelet  service did not start on one node after rebooting as part of the upgrade. There were no error messages observed in the vRSLCM and task will not fail. In  /var/log/bootstrap/postupdate.log  you see messages similar to: 2023-03-18 15:44:46Z /etc/bootstrap/postupdate.d/01-20-iptables starting... iptables.service is not active, cannot reload. 2023-03-18 15:44:46Z Script /etc/bootstrap/postupdate.d/01-20-iptables failed, error status 1 [INFO][2023-03-18 15:53:31][vra_fqdn] Waiting for VAMI to exit ... [INFO][2023-03-18 15:54:01][vra_fqdn] Verifying VAMI overall upgrade result ... [INFO][2023-03-18 15:54:01][vra_fqdn] VAMI upgrade completed with error. [ERROR][2023-03-18 15:54:01][vra_fqdn] VAMI overall upgrade has failed. VAMI has e...
Post a Comment
Read more
  Aria Automation upgrade fails with 'Error while deploying services' and 'vco-app' pods failing to come up fully Issue/Introduction Symptoms: Upgrade fails with 'Error while deploying services.' output of 'kubectl -n prelude get pods' shows most pods running but the 'vco-app' pods are only partially running. Checking 'vco'-app' logs we only see below errors: nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.symphony.csp.auth.service.CspClient]: Factory method 'cspClientService' threw exception; nested exception is java.lang.IllegalArgumentException:  expected system property https.proxyPort to be a number but got empty string Environment VMware Aria Automation 8.x Cause The issue occurs when the proxy service has been disabled using command vracli proxy disable. This should not be done unless consulted with VMware. The SOAP plugin requires the http.proxyPort property t...
Post a Comment
Read more