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
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.
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"