Overview

In this article, we provide step-by-step instructions to upgrade qTest Manager from 8.7.3 to 9.0 on multiple CentOS/Ubuntu machines using Docker. Please read the instructions thoroughly before starting your installations.

To request assistance with upgrading or obtain the self-upgrade links, complete the Upgrade Request Form and reference the OnPremise Upgrades Guide.

Note: If you are performing a fresh install, use the OnPremise New Install Form and reference the OnPremise Install Guide.

Before You Begin

Read the following:

• Getting Started with qTest OnPremise Spring 2018 

To upgrade qTest Manager from a version older than 8.7.3, please use our old Docker deployment packages.

 

Upgrade Example:

The example image below demonstrates how to configure qTest Manager with a load balancer for 4 machines:

• Machine 1: considered as a cluster, hosts qTest Manager's prerequisite apps:
  • Redis
  • RabbitMQ
  • Postgres
  • Poseidon
• Machine 2: hosts qTest Manager 9.0 (qtest)
• Machine 3: hosts qTest Manager 9.0 (qtest)
• Machine 4: hosts qTest Manager's load balancer (qtestlb)

Note: The cluster machine must open 2 ports:

• 53
• 6783

How to Upgrade Machine 2 and 3

Repeat all of the steps below for Machine 2 and 3 where you have installed qTest Manager 8.7.3 (qtest). No changes need to be made on Machine 1 and Machine 4 (qtestlb) servers.

Uninstall your Current Deployment

If your qTest Manager is set up as a Linux Daemon on this server, you should stop it first. If not, you can skip this step.

systemctl stop qtest

1. Access the directory where you've extracted the docker deployment package of qTest Manager 8.7.3 (docker-deployment-4.3), shut it down and create a backup.

   $ ./shutdown
   $ ./backup
   $ ./uninstall
   		

2. Download the Docker-Deployment-4.4 Package.
   Note: This package supports the upgrade of qTest Manager from version 8.7.3 to 9.0

   $ wget <ENTER DOWNLOAD LINK HERE>
   

3. Extract the package.

   $ tar -zxf docker-deployment-4.4.tar.gz
   

4. Access Docker-Deployment-x.x Directory.

   $ cd docker-deployment-4.4
   

Configure qTest Manager

You have 3 options::

1. To keep all applications in your previous deployment from being upgraded, override the /profiles directory of docker-deployment-x4.4 with the directory of docker-deployment-4.3

   $ cp -r /<path to your docker-deployment-4.3 package>/docker-deloyment-4.3/profiles/ .
   		

2. OR use configure command if you want to specify each application to be upgraded (for HTTP)

   $ ./configure --qtest-url "http://<IP of current machine>:<qtest port>" --qtest-http "<qtest port>"
   			

3. OR use configure command if you want to specify each application to be upgraded (for HTTPS)

   $ ./configure --ssl-key "<SSL Key>" --ssl-cert "<SSL Cert>" --ssl-ca "<SSL Ca>" --qtest-url "https://<IP of current machine>:<qtest https port>" --qtest-https "<qtest https port>"
   			

Upgrade qTest Manager

Upgrading will keep all of the current data for upgraded applications.

 $ ./upgrade

Deploy qTest Manager

1. Execute this command to initially set up and start the application.

   $ ./startup
   		

   The script will download the application images and qTest components to the Docker. It may take couple of hours depending on your network connection

2. Open your web browser, and access qTest Manager using the URL specified above.
3. Validate if qTest Manager has started successfully.
4. Execute these commands to set up qTest Manager as a Linux Daemon.

   $ ./shutdown
   $ ./install
   		

5. Start the service. You may need to wait for few minutes for qTest Manager to be available.

   $ systemctl start qtest
   		

Restart Machine 4

1. Access the directory where you've extracted the docker deployment package of qTest Manager 8.7.3 (docker-deployment-4.3.)
2. If your qTest Manager is set up as a Linux Daemon on this server, you should stop it first. If not, you can skip this step.

   $ systemctl stop qtest
   		

3. Shut down qTest Manager.

   $ ./shutdown
   		

4. Install qTest Manager as a Linux Daemon.

   $ ./install
   		

5. Start the service. You may need to wait a few minutes for qTest Manager to be available.

   $ systemctl start qtest