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 |
|---|---|---|
22.1 | 1965 | The TrueSight Automation Console installer |
22.1 | 2071 | The TrueSight Automation Console installer that contains the Spring4Shell fixes |
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:22.1.00.2071Here, 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.
ExampleName Container Name Version Status
---- -------------- ------- ------
PostgreSQL database-infra-ext-postgres 12-alpine running
Components status for application:
Name Container Name Version Status
---- -------------- ------- ------
Catalog service truesight-app-catalog-service 22.1.00.1068 running
Connector Service truesight-connectors-service 22.1.00.1489 running
Data Refresh Worker truesight-app-drw 22.1.00.328 running
Discovery OnPrem Connector truesight-common-discovery-onprem-connector 22.1.00.190 running
Exceptions-service truesight-common-exceptions-service 22.1.00.614 running
ITIL Service truesight-common-itil 22.1.00.489 running
Identity Management Service truesight-identitymanagement-service 22.1.00.1106 running
Login service truesight-common-login 22.1.00.1024 running
Nginx truesight-app-nginx 22.1.00.1052 running
Organization Service truesight-organization-service 22.1.00.346 running
Patch Manager portal truesight-app-patch-manager-portal 22.1.00.9897 running
Patch Manager service truesight-app-patch-manager-core 22.1.00.1618 running
Platform Portal truesight-platform-portal 22.1.00.1448 running
Policy service truesight-app-policy-service 22.1.00.1637 running
Redis truesight-infra-ext-redis 22.1.00.495 running
Redis-common truesight-infra-ext-redis-common 22.1.00.495 running
Resource service truesight-common-resource-service 22.1.00.790 running
TSNA Connectortruesight-common-tsna-connector 22.1.00.474 running
TSO Connector truesight-common-tso-connector 22.1.00.355 running
TSSA Connector truesight-common-tssa-connector 22.1.00.688 running
Tenable Connector truesight-common-tenable-connector 22.1.00.138 running
Tenant Onboarding Utility truesight-common-tenant-onboarding-utility 22.1.00.327 running
Users Service truesight-users-service 22.1.00.417 running
configurations-service truesight-configurations-service 22.1.00.145 running
rsso-portal truesight-rsso-portal 22.1.00.202 running
workmanager-service truesight-workmanager-service 22.1.00.490 runningTo verify the version<install_directory>/stackmanager versionThe following figure shows the sample version.
ExampleService Version
------- -------
Catalog service 22.1.00.1068
Connector Service 22.1.00.1489
Data Refresh Worker 22.1.00.328
Discovery OnPrem Connector 22.1.00.190
Exceptions-service 22.1.00.614
ITIL Service 22.1.00.489
Identity Management Service 22.1.00.1106
Login service 22.1.00.1024
Nginx 22.1.00.1052
Organization Service 22.1.00.346
Patch Manager portal 22.1.00.9897
Patch Manager service 22.1.00.1618
Platform Portal 22.1.00.1448
Policy service 22.1.00.1637
Redis 22.1.00.495
Redis-common 22.1.00.495
Resource service 22.1.00.790
TSNA Connector 22.1.00.474
TSO Connector 22.1.00.355
TSSA Connector 22.1.00.688
Tenable Connector 22.1.00.138
Tenant Onboarding Utility 22.1.00.327
Users Service 22.1.00.417
configurations-service 22.1.00.145
rsso-portal 22.1.00.202
workmanager-service 22.1.00.490- (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.