Failed to install updates(Error while running post-install scripots)
VA-check: finished
Pre-install: finished
Post-install: failed
Update failed (code 0-2). Check logs in /opt/vmware/var/log/vami or retry update later.
/var/log/bootstrap/postupdate.log
file, you see the entries similar to:Orchestrator Configuration Tool. Version: 7.4.0.8071781 Build: 8071781
Can not read the Orchestrator pid from /var/lib/vco/app-server/logs/tomcat.pid
Start configuring database settings.
Configuring database settings finished successfully.
Start updating database scheme.
ch.dunes.vso.db.check.CheckDuplicatesException:
Duplicate entries found in the Orchestrator database:
System tables duplicates:
2 items with ID '<UUID>' in database table 'vmo_scriptmodulecontent'
.
.
Resolve duplicates by deleting unnecessary items.
java.lang.RuntimeException: ch.dunes.vso.db.check.CheckDuplicatesException:
Duplicate entries found in the Orchestrator database:
Resource element duplicates:
1 item with ID '<UUID>' and name 'ko.properties'
1 item with ID '<UUID>' and name 'fr_FR.properties'
1 item with ID '<UUID>' and name 'zh_CN.properties'
(and many more)
Duplicates found in the embedded vRealize Orchestrator database:
- 1 items in table vmo_configelement: ID=xxxxxxxxxxxxxxxxx NAME=InstanceDetails
- 1 items in table vmo_configelement: ID=xxxxxxxxxxxxxxxxx NAME=General
- 1 items in table vmo_configelement: ID=xxxxxxxxxxxxxxxxx NAME=Allocation
Script /etc/bootstrap/preupdate.d/00-00-02-check-vro-duplicates failed, error status 1
VMware vRealize Automation 7.x
VMware is aware of this issue.
A resolution for this issue is being evaluated for inclusion in a future release.
To work around this issue when vRO is using the embedded vRA psql database, perform the following steps:
vco-cfg-cli-7.4.0.23640-8992942.noarch.rpm
file to a directory on your vRealize Automation appliance.rpm -hiv vco-cfg-cli-7.4.0.23640-8992942.noarch.rpm
/usr/lib/vco-cli/bin/vro-configure.sh db-validate
su postgres
/opt/vmware/vpostgres/current/bin/psql vcac
delete from vmo_resourceelement where categoryid = 'xxxxxxxxxxxxxxxxx' and name = 'de_DE.properties';
delete from vmo_configelement where categoryid = 'xxxxxxxxxxxxxxxxx' and name = 'de_DE.properties';
\q
/usr/lib/vco-cli/bin/vro-configure.sh db-validate
The command does not need a database configuration update.
In 7.5 and 7.6 the upgrade automatically checks for duplicates and reports on those tables that are duplicates. Once duplicates are found you need to delete the duplicates. You may run the below command to check after deletion that all tables are removed.
cd /usr/lib/vco/tools/configuration-cli/bin/
command : ./vro-configure.sh db-validate
Orchestrator's root folder: /var/lib/vco
Orchestrator Configuration Tool. Version: 7.6.0.12923317 Build: 12923317
ValidateDbOptions{dbUsername='vmware', dbPassword='****', jdbcUrl='jdbc:postgresql://localhost:5433/vmware?sslmode=verify-ca&sslrootcert=/var/vmware/vpostgres/current/.postgresql/root.crt'}
The command does not need database configuration update.
Login to Orchestrator Client as Design user.
Enter the Name output in the output in the NAME field output by upgrade.
Open each duplicate and make note of the one with the most relevant content that you wish to keep.
Right Click on the one you wish to remove and delete.
The auto-creation of an item means there is a running vRO process connected to your database. You must stop it and then delete the duplicate entry. The missing version history items are not critical and even they miss in different situations so it is not that important which one gets deleted.
Duplicates found in the embedded vRealize Orchestrator database:
- 1 items in table vmo_versionhistorycontent: ID= NAME=1.0.800
- 1 items in table vmo_versionhistorycontent: ID= NAME=-1.0
4. Configuration elements are flagged as duplicate:
Login to the Orchestrator Client
Search for the GUID
Remove the duplicate element.
Duplicates found in the embedded vRealize Orchestrator database:
- 1 items in table vmo_configelement: ID=xxxxxxxx NAME=InstanceDetails
- 1 items in table vmo_configelement: ID=8xxxxxxxx NAME=General
- 1 items in table vmo_configelement: ID=xxxxxxxx NAME=Allocation
Script /etc/bootstrap/preupdate.d/00-00-02-check-vro-duplicates failed, error status 1
5. Corrupted, duplicate workflow tokens:
com.vmware.o11n.bug_2444547.package
/storage/db/pgdata/pg_hba.conf
file to allow local connections from source IP:
host all all x.x.x.x/24 md5
service vpostgres restart
7. Extract PSQL password and decrypt:
cat /etc/vcac/server.xml |grep password="*"
/usr/lib/vcac/tools/config/bin/vcac-config prop-util -d --p s2enc~xxxxxxxxxx+PGEaI= |less
Example password Output:
xxxxxxxxo*nS
8. Create a new SQL Plugin host connection within the vRealize Orchestrator client by running the workflow named: "Library > SQL > Configuration > Add a database"
Name: "Local vPostgres Instance"
Database Type: postgreSql
Connection URL: jdbc:postgresql://vra fqdn:5432/vcac
"Next"
"Shared Session"
vcac
xxxxxx*nS
9. Execute the workflow: "Delete Corrupted WorkflowTokens"
1. Reattempt the upgrade.