+ /etc/bootstrap/postupdate.d/00-00-rpm-status-check 7.2.0.381 7.3.0.536 4 + res=1 + echo 'Script /etc/bootstrap/postupdate.d/00-00-rpm-status-check failed, error status 1' + exit 1 + exit 1 + trapfunc + excode=1 + test 1 -gt 0 + vami_update_msg set post-install 'Post-install: failed' + test -x /usr/sbin/vami-update-msg + /usr/sbin/vami-update-msg set post-install 'Post-install: failed' + sleep 1 + test 1 -gt 0 -o 4 -gt 0 + vami_update_msg set update-status 'Update failed (code 4-1). Check logs in /opt/vmware/var/log/vami or retry update later.' + test -x /usr/sbin/vami-update-msg + /usr/sbin/vami-update-msg set update-status 'Update failed (code 4-1). Check logs in /opt/vmware/var/log/vami or retry update later.' + exit <YYYY-MM-DD>T<time> [ERROR] Failed with exit code 256</time>
In the vRA Appliance, the folder /usr/ssl/certs/ already exists.
Cause
This issue occurs due to the /usr/ssl/certs/ folder which is not expected under normal circumstances and causes the upgrade to fail initially. This folder may exist if the environment has configured vRealize Log Insight to communicate with a system that does not use self-signed certificates.
Resolution
This issue is resolved in VMware vRealize Automation 7.4.
To work around this issue,
Re-run the upgrade a second time and it should allow for completion.
If re-running the upgrade does not resolve the issue:
Backup the directory by moving the files from /usr/ssl/certs to /etc/ssl/certs.