Skip to main content

 

New installs of vRealize Orchestrator 8.x fail to install due to a POD STATUS of 'CrashLoopBackOff'


Issue/Introduction

Symptoms:

When deploying a new installation of vRealize Orchestrator 8.x, or vRealize Automation 8.x with embedded vRealize Orchestrator 8.x, you may experience the following:

  • vRealize Suite Lifecycle Manager displays a failure to initialize the VRA cluster with the error LCMVRAVACONFIG590003.

  • The Kubernetes pod for vco-app-<ID> fails to start with 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

  • Confirm the error by running the following command on the appliance:

kubectl -n prelude logs vco-app-<ID from previous command> -c install-rpms

  • The vco-app-<ID> container log contains the following error:

You are required to change your password immediately (password expired)
groupadd: PAM: Authentication token is no longer valid; new one required
useradd: group 'vco' does not exist
error: %prein(vco-server-8.1.0.1576591045-15331417.noarch) scriptlet failed, exit status 6
error: vco-server-8.1.0.1576591045-15331417.noarch: install failed

Environment

VMware vRealize Automation 8.x
VMware vRealize Orchestrator 8.x

Cause

The deployed vRealize Orchestrator container may be created with an expired password causing packages to fail and the container to crash.

Resolution

Workaround:
To work around this issue, use the following steps:

  1. Log into the Appliance with SSH.
  2. Navigate to /opt/charts/vco/templates/
  3. Copy/Backup the deployment.yaml file using the command:
cp deployment.yaml /tmp/

NOTE:  Do not copy any backup.yaml files into /opt/charts/vco/ or /opt/charts/vco/templates/.  Doing so will result in 404 errors after successful service restart.
  1. Edit the deployment.yaml file using your preferred editor (vi deployment.yaml).
  2. Locate the string:  init_run.sh
  3. Replace the text as follows.
Search for row that contains this text: init_run.sh:
command:
- "/bin/bash"
- "-c"
- "/init_run.sh"

Edit this row by just adding these two "sed" commands before /init_run.sh script. The row after editing should looks similar to this::
command:

- "/bin/bash"
- "-c"
- "sed -i 's/root:.*/root:x:18135:0:99999:7:::/g' /etc/shadow && sed -i 's/vco:.*/vco:x:18135:0:99999:7:::/g' /etc/shadow && /init_run.sh"
  1. Save the file
If you are deploying outside of vRealize Suite Lifecycle Manager, follow these steps:
  1. Navigate to /opt/scripts/
  2. Execute the script: ./deploy.sh
If you are deploying through vRealize Suite Lifecycle Manager, follow these steps:
  1. Log back into Lifecycle Manager and 'Retry' the deployment that failed.  Installation should now progress as expected.
Labels:

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