IBM Support

Rational Test Automation Server V10.1.1



IBM Rational Test Automation Server V10.1.1 was made generally available and contains features and fixes for customer-reported and internally found defects.

Download Description

Table of Contents
Sections Description

The Change history section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable.

The How critical is this fix section provides information related to the impact of this release to allow you to assess how your environment may be affected.

The Prerequisites section provides important information to review prior to the installation of this release.

The Download package section provides the direct link to obtain the download package for installation in your environment.

The Installation instructions section provides the installation instructions necessary to apply this release into your environment.

The Known side effects section contains a link to the known problems (open defects) identified at the time of this release.

Supporting Documentation
Document Description

Click to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.

IBM Product Documentation provides an entry point to the documentation. You can view, browse, and search the online information.


Prerequisites include:

Review Prerequisites for installing the server software on Red Hat OpenShift or Prerequisites for installing the server software on Ubuntu in the IBM Product Documentation prior to installing.

Installation Instructions

Review Installation of server software on Red Hat OpenShift or Installation of server software on Ubuntu in the IBM Product Documentation.

Review the Upgrading the software page in the IBM Product Documentation before you install.

Download Package

Download options
Access type Description

Passport Advantage and Passport Advantage Express clients are required to sign in to download the software package.

If you are entitled for Rational Test Automation Server and need to download your software from Passport Advantage, perform the following steps:

  1. Logon to Passport Advantage.
  2. Select Software Downloads and Media Access.
  3. Select the Download Finder.
  4. Select Find by description or part number.
  5. Select the Product Description and All radio buttons and enter Rational Test Automation Server in the description field.
  6. Select Continue.
  7. Expand the eAssemblies and you will see your entitled software.

IBM Software Group OEM offerings are designed for partners who develop and sell business solutions with embedded or bundled IBM middleware software. Clients with Flexible Contract Type (FCT) license purchases and IBM Business Partners must sign in to download the software package.

How critical is this fix?

Impact Assessment
Impact Description

This is a service release. It contains new features as well as fixes for client-reported and internally found defects.

Test Results


Regression: An error in the Maintenance Delivery Vehicle (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed.
This includes:

  • Coding errors that cause a regression
  • Documentation or packaging problems that cause a regression
  • Errors reported in a new function delivered in a MDV that cause a regression

Incomplete: An error in the MDV has not regressed, but does not work as designed.
This includes:

  • Fixed APARs which did not solve the original problem but did not break anything new
  • APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression

  • Regression and incomplete APARs are considered fix-in-error or MDV-in-error
  • Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)
  • Issues in major releases due to new functionality do not apply in this definition

There are no known regressions to report.

Problems Solved

Known Side Effects

Review the following list of known issues and open defects:

Review the following list of known issues.

Rational Test Automation Server is a product of IBM's comprehensive test solution.  Fix packs are made available separately.

Review technote 1461170: Open APARs for Rational products available on the Web for information on how to configure your MyNotifications subscription account and subscribe to the APARs you are interested in following.

Known issues in this release include:

New to this release
When you install Rational Test Automation Server V10.1.1 on an OpenShift platform where OpenShift Container Storage (OCS) is not available (For example, the IBM Cloud) then test asset runs fail. This is because the default storage class does not support ReadWriteMany (RWX). 

To work around this problem, you must specify the following helm parameter during the server install: 

--set execution.userlibs.persistence.storageClass=ibmc-file-bronze 
TP-69650 When you run the script to set up the Kubernetes environment and if the snap command is unavailable, then the command-line interface incorrectly displays the following error message for snapd: 

./ line 232: ehco: command not found 

The intended message is: 

Error: snapd is not installed 
Please ensure that snapd and snap are installed correctly, for example: 
sudo apt-get install snapd         
TP-66731 You might experience errors when you publish large reports, either from desktop products or when executing a test on the server. 

To circumvent this problem, it is recommended that you first try to reduce your reports size by reducing the logging or details level. 
If the detail level cannot be reduced, you can increase the server limits to support larger reports. 
To do so, you must rerun the helm command that was performed when you installed the server software and add the following arguments: 

--set-string ingress.annotations.nginx\\.ingress\\.kubernetes\\.io/proxy-body-size=2g 
--set resources.limits.memory=4Gi 

This example enables the server to accept up to 2 GB reports. This comes at the expense of a higher memory requirement. It is usually recommended to set the "resources.limits.memory" to 2 GB over the reports size limit.
TP-66834 During the installation, when you migrate user data from the previous version to V10.1.0, the datasets database does not restore properly. As a result, Data classification information is disappeared from Rational Test Automation Server. 

You must classify the encrypted dataset again by creating a new classification.   

When you back up user data of V10.1.0 and restore it on V10.1.1 in the Ubuntu environment, one of the pods does not start. This problem occurs occasionally.

For example, if the result pod does not start, to work around this problem, perform the following steps:
Note: In the following commands, <myrtas> refers to the release name of your choice and <namespace> refers to the name of the namespace that you created during the server installation process.

1. Increase the value of initialDelaySeconds in the following command to start the service:

kubectl patch sts -n <namespace> <myrtas>-results --patch '{"spec": {"template": {"spec": {"containers": [{"name": "results","readinessProbe":{"initialDelaySeconds":180}}]}}}}'

2. Get the database password by running the following command:

kubectl get secret -n <namespace> <myrtas>-results -o jsonpath="{.data.postgresql-password}" | base64 --decode

3. Delete the troublesome database lock by running the following command:

kubectl exec -n <namespace> <myrtas>-results-postgresql-0 -i -- sh -c 'PGPASSWORD=<password> psql -U results -d results -c "DROP TABLE DATABASECHANGELOGLOCK"'

4. Restart the pod by running the following command:

kubectl delete pod -n <namespace> <myrtas>-results-0

Previous known issues that still apply
TP-59943 If you configure Keycloak to use an LDAP directory service, you should import and synchronize LDAP users to Keycloak. This is a known issue with Keycloak: 

To workaround the problem in Keycloak, on the Add user federation provider page make sure the following settings are set as shown: 
Import Users = ON, Sync Registrations = ON, and Cache Policy = DEFAULT
TP-66941 You cannot run tests on the remote static agents connected to Rational Test Automation Server that is installed in an OpenShift environment.   
TP-67330 When you look at the pod restart statistic with kubectl get pods -n test-system even after the server was idle for a while, you might observe a high number of restarts of the kafka pod and some restarts of other microservices. However, the server is up and running. 

This issue is known and shows that the Kubernetes orchestrator has cycled the Kafka pod because of the sensitivity of the readiness and liveness probes. There is no user action required as the situation finally stabilizes automatically. 
TP-67215 When you configure Rational Test Automation Server test on the UCD server and you enter a value for any of the options available for Show Hidden Properties in the Edit Properties for Run Rational Test Automation Server test window, the values for the options do not work as designed during the test run.

To work around this problem, you must not set any values for any options for Show Hidden Properties.
TP-61446 When you unregister a remote docker agent, running and schedule tests are not canceled. 

To workaround this problem, stop any running tests and cancel any scheduled future executions for that agent before unregistering the remote docker agent.
TP-62379 If you (as a user) request to join an orphaned project, a 404 not found error results.

To workaround this problem, ask your administrator to become the project owner, then request to join that project again.
TP-61311 When you archive a project that has a running test, that test is not stopped. The test completes execution even though it was suppose to stop.
TP-61494 If you unarchive a project that was archived while a test was running, the UI incorrectly shows that the test is still running after the unarchive.

To workaround this problem, make sure there are no tests running when you archive a project.
TP-61446 When you unregister a remote docker agent, running and schedule tests are not canceled.

To workaround this problem, stop any running tests and cancel any scheduled future executions for that agent before unregistering the remote docker agent.
TP-60059 When you schedule a test run and click the "Time" field a list of times displays. If you enter a value in the "Time" field, you cannot move the cursor by using the left or right (<- , -> ) keyboard keys. This is a known issue with the following date picker:

To workaround this problem, use the cursor.
TP-58061 A server shutdown will not stop currently running executions. It is recommended to not shutdown the server if there are active executions running. If the server is shut down while assets are executing the reported status of those executions might be incorrect.
TP-58017 In case of a slow network, the cloning of a repository might fail with an error. In such a case, you can delete and add the repository again.

When working in multiple Rational Test Automation Server tabs concurrently, a message “You are already logged in” might sometimes be displayed. This message occurs when your session has expired and you have since logged in again, but then attempt a navigation action in a browser tab other than the one in which you logged in.

This is a known Keycloak issue. For more information, see To workaround this problem, close the tab and open a new one.

TP-56453 After about 20 minutes of an inactive browser session for Rational Test Automation Server, if you attempt to use the existing browser session, you must authenticate again by providing your username and password. When you do so, the message "You took too long to log in. Try again.“ is displayed and you must enter your credentials again.
Rational Performance Tester Agent

With 10.0, you might expect a reduction in the number of Virtual Users (VUs) supported by IBM Rational Performance Tester Agent depending upon workload characteristics. This variation is the result of the product shipping with OpenJDK™ 8 with OpenJ9 instead of IBM JRE.

OpenJDK 8 with OpenJ9 JRE exhibits a higher utilization of CPU for the workload. Up to 30% or more decrease in the supported VUs capacity may be expected for CPU-bound workloads. However, for memory-bound workloads, a much smaller, if any reduction in VUs capacity may be expected.

If you need higher performance and have access to IBM JRE or later that contains the latest security fixes, you can switch from OpenJDK 8 with OpenJ9 to IBM JRE. For more information, see

Change History

What's new

Review the Release notes in the IBM Product Documentation for a complete list of new features and enhancements.


Technical Support


Tab navigation



IBM Rational Software Support Communities

  • Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.

  • Visit IBM Developer to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.

  • Visit the Jazz Community if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track developement progress.

Helpful Hints For Obtaining Technical Assistance:


Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

  • What software versions were you running when the problem occurred?
  • Do you have logs, traces, or messages that are related to the problem?
  • Can you reproduce the problem? If so, what steps do you take to reproduce it?
  • Is there a workaround for the problem? If so, be prepared to describe the workaround.

If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.


[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS6QK3","label":"IBM Rational Test Automation Server"},"ARM Category":[],"Platform":[{"code":"PF016","label":"Linux"}],"Version":"10.1.1"}]

Document Information

Modified date:
07 October 2020