Overview

In the qTest 9.7.1 OnPremise package, the following have been remediated with the qtestctl-6.4 patch. 

•  Insights 1.21.9.1 caused some customers to experience a 403 error when attempting to access Insights from the 9-box. This has been fixed with the release of Insights 1.21.9.2 that is included in this patch.
• Java Core was upgraded from Oracle JDK 1.8_144 to Open JDK 1.8_212 which impacted customers using LDAPS (LDAP with a secure protocol.) This is fixed and included in this patch.

Below are instructions for replacing the previous 9.7.1 package.

Linux / Windows patching (for qtestctl)

1. Stop the qtest service using the commands below:

   • Windows: net stop qtest

   • Linux: systemctl stop qtest

2. Uninstall the qtest service by going to the qtestctl/ directory, and run the following command:

   • Windows: uninstall.bat

   • Linux:  ./uninstall

3. Rename the current qtestctl/ (9.7.1) to:
   

   qtestctl_old/

4. Download the new installation package provided by Implementations, and extract to the server.
5. Use the appropriate upgrade guide to install the patch (Re-Upgrade from 9.6.1 to 9.7.1 package.)
   • Linux:
     • Single Server Upgrade Guide
     • Load Balance Upgrade Guide
   • Windows:
     • Single Server Upgrade Guide
     • Load Balance Upgrade Guide
6. After upgrading successfully, you can clean up the qtestctl_old/ folder from step 3.

Docker

1. Shutdown the qtest application with the following command:

    ./shutdown

2. Uninstall the qtest service by using the following command:

    ./uninstall

3. Rename the current docker-deployment package to:

    docker-deployment_old

4. Download new docker-deployment package and extract to the server.
5. Clean the qtest cache folder ($cache_dir in docker-deployment/profiles/default.in)
6. Use the following upgrade guide to install the patch:
   • Single Server Upgrade Guide
   • Load Balance Upgrade Guide 
7. After upgrading successfully, you can clean up the docker-deployment_old from step 3.

Verification

Manager

• From your browser, go to your qTest environment.
  Ex : http(s)://QTEST_URL/version

Expected result:

{
 "name": "test-conductor",
 "version": "9.7.1",
 "timestamp": "2019-08-14 05:18:08+0000",
 "revision": "a08c3a8",
 "branch": "UNKNOWN",
 "builder": "jenkins",
 "buildNumber": "${build.number}",
 "env": "onpremise",
 "envRaw": "onpremise"
}

Insights

• From your browser, go to your Insights environment.
  Ex: http(s)://INSIGHTS_URL/version

Expected result:

{
  "name": "qTest Insights",
  "version": "1.21.9",
  "branch": "v1.21.9.2.op",
  "revision": "2d18f00",
  "build_time": "2019-08-23T10-48-16 +0000",
  "commit_time": "2019-08-23T10-45-55 +0000",
  "etl_version": "unknown"
}