Performing the upgrade
During an upgrade, you only upgrade the application, which also upgrade the underlying database schema.
Build numbers
You must provide the build number depending on the version that you want to upgrade to.
Version | Build number | Details |
|---|---|---|
23.1 | 2475 | The TrueSight Automation Console installer |
To upgrade TrueSight Automation Console
Open a terminal and SSH into the host where you have set up the local registry, and run the following command to update the Stack Manager tool.
docker run -it --rm --network=host <hostname>:<port>/bmcsoftware/truesight-stack-manager:<version_number>.<build_number>Exampledocker run -it --rm --network=host 127.0.0.1:5000/bmcsoftware/truesight-stack-manager:23.1.00.2475Here, 127.0.0.1:5000 is the host:port of the local registry that contains the TrueSight Automation Console images.
You are prompted to specify a location to install the product.- Enter a username with root permissions and a password.
The Stack Manager tool is updated at the specified location. - Enter the location where the previous version is installed.
The following message is displayed: Stack Manager Launcher is already installed, do you want to overwrite it?y/(n) - Enter y.
The Stack Manager tool is updated. On the host where the Stack Manager tool is installed, run any of the following commands to start upgrading the application.
This command also upgrades the database schema.<install_directory>/stackmanager install --deployment tsac+<install_directory>/stackmanager install --deployment=tsac+The existing installation and the END USER LICENSE AGREEMENT is displayed.
[INFO] loading deployment registry from /opt/bmc/sm/registry/sm-deployment-registry.yml
**************************************************
TrueSight Stack Manager <version_number>.<build_number>
**************************************************
The following services are already installed:
Deployment Location
---------- --------
application /opt/bmc/truesight/application
database /opt/bmc/truesight/database
[INFO] Start installation
Press Enter to Read the License Agreement and enter the Appropriate Option
END USER LICENSE AGREEMENT
<Agreement Text>Read, and type y to continue with the upgrade.
If you are upgrading to 21.02.01 or later versions, the following message appears: Do you want to configure TSNA Connector [You may choose No now & configure it post upgrade] ([y]es/[n]o) ?(Optional) If you choose to configure the TrueSight Network Automation connector, type y and provide the values that match your environment:
If you do not want to configure the connector, type n and skip to step number 8.Field
Description
Host name of TrueSight Network Automation
Fully-qualified domain name or IP address of TrueSight Network Automation
Port number of TrueSight Network Automation
Port number
Protocol of TrueSight Network Automation
Default value: https
Realm name of TrueSight Network Automation
Specify the realm name
Service Account user name of TrueSight Network Automation
Specify the user name
Password for the Service Account user of TrueSight Network Automation '<user name>'
Specify the password that matches the user name
Realm name for the Service Account user of TrueSight Network Automation <Realm Name>
Specify the realm name of the service account user
TrueSight Automation Console upgrade is complete and the following status message appears.
TrueSight Automation Console <build_number> can be accessed at: <URL>
Installation is completed successfully.
<For 21.02.01 or later versions>
TrueSight Automation Console <version_number>.<build_number> can be accessed
at: https://<hostname>:<portnumber>/services/#/account/tsna/loginTo verify whether the upgrade is successful, run the following command:
To verify the status<install_directory>/stackmanager status --deployment=applicationThe updated services, container names, versions, and their status is displayed.
Name Container Name Version Status
---- -------------- ------- ------
Activity Log service truesight-app-activity-log-service 23.1.00.242 running
Catalog service truesight-app-catalog-service 23.1.00.1527 running
Connector Service truesight-connectors-service 23.1.00.2712 running
Data Refresh Worker truesight-app-drw 23.1.00.693 running
Discovery OnPrem Connector truesight-common-discovery-onprem-connector 23.1.00.513 running
Exceptions-service truesight-common-exceptions-service 23.1.00.986 running
ITIL Service truesight-common-itil 23.1.00.863 running
Identity Management Service truesight-identitymanagement-service 23.1.00.1441 running
Login service truesight-common-login 23.1.00.1381 running
Nginx truesight-app-nginx 23.1.00.1288 running
Organization Service truesight-organization-service 23.1.00.684 running
Patch Manager portal truesight-app-patch-manager-portal 23.1.00.10320 running
Patch Manager service truesight-app-patch-manager-core 23.1.00.2102 running
Platform Portal truesight-platform-portal 23.1.00.1787 running
Policy service truesight-app-policy-service 23.1.00.2194 running
Redis truesight-infra-ext-redis 23.1.00.884 running
Redis-common truesight-infra-ext-redis-common 23.1.00.884 running
Resource service truesight-common-resource-service 23.1.00.1107 running
TSNA Connector truesight-common-tsna-connector 23.1.00.1525 running
TSO Connector truesight-common-tso-connector 23.1.00.487 running
TSSA Connector truesight-common-tssa-connector 23.1.00.1298 running
Tenable Connector truesight-common-tenable-connector 23.1.00.1472 running
Tenant Onboarding Utility truesight-common-tenant-onboarding-utility 23.1.00.774 running
Users Service truesight-users-service 23.1.00.732 running
configurations-service truesight-configurations-service 23.1.00.481 running
rsso-portal truesight-rsso-portal 23.1.00.517 running
workmanager-service truesight-workmanager-service 23.1.00.834 running
To verify the version<install_directory>/stackmanager versionThe following figure shows the sample version.
Service Version
------- -------
Activity Log service 23.1.00.242
Catalog service 23.1.00.1527
Connector Service 23.1.00.2712
Data Refresh Worker 23.1.00.693
Discovery OnPrem Connector 23.1.00.513
Exceptions-service 23.1.00.986
ITIL Service 23.1.00.863
Identity Management Service 23.1.00.1441
Login service 23.1.00.1381
Nginx 23.1.00.1288
Organization Service 23.1.00.684
Patch Manager portal 23.1.00.10320
Patch Manager service 23.1.00.2102
Platform Portal 23.1.00.1787
Policy service 23.1.00.2194
PostgreSQL 14-alpine
Redis 23.1.00.884
Redis-common 23.1.00.884
Resource service 23.1.00.1107
TSNA Connector 23.1.00.1525
TSO Connector 23.1.00.487
TSSA Connector 23.1.00.1298
Tenable Connector 23.1.00.1472
Tenant Onboarding Utility 23.1.00.774
Users Service 23.1.00.732
configurations-service 23.1.00.481
rsso-portal 23.1.00.517
workmanager-service 23.1.00.834- (Optional) If you are using custom certificates, ensure that you have backed up the certificate files before the upgrade. After a successful upgrade, do these steps:
Run the following command to replace the new certificates (created during the upgrade) with the custom certificates copied earlier.
cp /opt/<backup_directory>/tsvmSslCertificate.crt <install_dir>/application/common/certs/
cp /opt/<backup_directory>/tsvmSslCertificate.key <install_dir>/application/common/certs/Restart the application.
<install_directory>/stackmanager restart --deployment=application
Where to go next?
After a successful upgrade, the previously installed connectors do not need any update. If you want to configure any of the new/optional connectors, see Managing-connectors.