Skip to main content

 Aria Automation 404 page not found - vco container is not starting

https://knowledge.broadcom.com/external/article?articleNumber=376562

Products

VMware Aria Suite

Issue/Introduction

  • In Aria Automation, after a network disruption, the UI shows 404 page not found. 
  • The Kubernetes pod for vco-app-<ID> shows a STATUS of 'CrashLoopBackOff'.  
  • To confirm this, run the following command on the appliance:
         kubectl -n prelude get pods
  • The status of the vco-app pod is CrashLoopBackOff
  • Deploy.sh fails with an error starting pods. 

Environment

Aria Automation 8.x

Cause

A network disruption at the environment will cause service isolation, which might result in service / pod CrashLoopBackOff

Resolution

Shut down Automation services and reboot the appliance before starting the services again:

  1. Log into one appliance via SSH or console as root
  2. Shutdown Automation Services by running:
         /opt/scripts/deploy.sh --shutdown
  3. Wait for the script to finish
    running 'kubectl -n prelude -get pods' should not show any running pods
  4. Reboot the appliance(s)
  5. Open the remote Console to the Automation appliance in vCenter and wait for the blue Login screen to available on all Automation appliances.
  6. Login to one appliance via the Console or SSH as root
  7. Start the Automation services by running:
         /opt/scripts/deploy.sh
  8. Wait for the deploy.sh script to finish successfully. 

Additional Information

  • For a clustered deployment, the deploy.sh --shutdown only needs to be performed on 1 out of the 3 nodes. 

Comments

Post a Comment

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 πŸ”Ή Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more