Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
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 requireduseradd: group 'vco' does not existerror: %prein(vco-server-8.1.0.1576591045-15331417.noarch) scriptlet failed, exit status 6error: vco-server-8.1.0.1576591045-15331417.noarch: install failed
The deployed vRealize Orchestrator container may be created with an expired password causing packages to fail and the container to crash.
See Builtin containers root password expires preventing installations for vRealize Automation 8.0 and 8.0.1 or cumulative update patches on existing deployments
To work around this issue, use the following steps: Log into the Appliance with SSH.Navigate to /opt/charts/vco/templates/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. Edit the deployment.yaml file using your preferred editor (vi deployment.yaml).Locate the string: init_run.shReplace 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" Save the file If you are deploying outside of vRealize Suite Lifecycle Manager, follow these steps: Navigate to /opt/scripts/Execute the script: ./deploy.sh If you are deploying through vRealize Suite Lifecycle Manager, follow these steps: Log back into Lifecycle Manager and 'Retry' the deployment that failed. Installation should now progress as expected.