Workarounds and Limitations: Known issues in IBM Rational Quality Manager 6.0.5

Licensing errors might occur if you upgrade the Java environment or upgrade applications to version 6.0.5 or later

First occurrence
6.0.5

Problem
If you upgrade your version of Java to a fix pack that was built after April 2017, or you upgrade an application to version 6.0.5 or later and are using WebSphere Liberty, licensing errors might occur. The errors occur because earlier licenses were signed with the MD5 algorithm, which is now blocked by newer versions of Java.

For example, the License Key Management page for Jazz Team Server might display the following error in the Description field: CRJAZ1236I A development time license is being used. Similarly, the jts.log file might display the following error: CRJAZ0965I The file was not a valid server or client access license activation key.

The latest license files no longer contain the MD5 algorithm because IBM and Oracle Java introduced restrictions on JAR files that are signed with weak algorithms and keys.

Workaround
The licenses in the IBM Rational License Key Center were updated to use a different signature algorithm.

After you upgrade your server to version 6.0.5 or later, obtain the updated licenses from the IBM Rational License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses.

Important: If you are not upgrading all applications at the same time, you must apply an interim fix to the applications at earlier versions before you upgrade Jazz Team Server. The following interim fixes contain the compatible version of Java:

• 6.0.4 interim fix 007 and later
• 6.0.3 interim fix 010 and later
• 6.0.2 interim fix 015 and later
• No version of 5.0.2 contains a compatible Java version. For 5.0.2, complete the steps in the IBM Support flash article.

If you cannot apply the interim fix before the upgrade, upgrade Jazz Team Server and then complete the steps in the IBM Support flash article. If you do not apply the interim fix or complete the steps in the article, the internal licenses do not load on Jazz Team Server and the applications might experience issues.

To update your current license files, follow the instructions in the Interactive Upgrade Guide or complete the following steps based on the type of license:

For term (floating or authorized user) or token licenses:

Note: For token licenses, you are only required to download the jazztokens.zip file. You do not have to download the license.dat file because it does not contain changes.

1. Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
2. In IBM Rational License Key Center, under License Management, click Return Keys.
3. Click the product link that you want to return the license keys for, and then click Return.
4. After the license is returned, click Get Keys.
5. Click the product link to generate licenses for.
6. When prompted, provide the required information and click Generate.
7. Download the  file that contains the new licenses.
8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.

For non-term floating and authorized user licenses:

1. Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
2. In IBM Rational License Key Center, go to View keys by host or View keys by user.
3. Enter the information about the host or the user.
4. Select the product to generate the license for.
5. Click View Licenses for Selected Product Lines.
6. Select the license and click View Details.
7. Click Download Keys.
8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.

Note: If you imported trial licenses before the newer versions of Java were adopted, you might still receive errors in the jts.log file even after you import the updated licenses. For example, you might receive this error: CRJAZ0965I The file was not a valid server or client access license activation key. You can ignore these errors.

Related information
IBM Rational License Key Center
Interactive Upgrade Guide
Oracle release note: Restrict JARs signed with weak algorithms and keys

Snapshots of test plans with a large number of test artifacts might cause an error

First occurrence
6.0.5

Problem
When you create a snapshot of a test plan that has a large number of test artifacts, an error message such as 500: Unable to save snapshot for TestPlan might be displayed. The snapshot might be created successfully, but the error can occur if the session times out with an HTTP proxy server.

Workaround
Increase the session timeout setting for the HTTP proxy server. In Rational Quality Manager, the default session timeout setting is 6 hours: consider increasing the timeout setting for the HTTP server to the same value.

Related information
Work Item 166727
Rational Quality Manager Default Session Timeout

Command-line adapter cannot connect to the QM server by using smart card authentication

First occurrence
6.0.4

Problem
If you use the command-line adapter to connect to the Quality Management (QM) server, smart card authentication does not work.

Workaround
Complete these steps:

1. Update the Java SDK to IBM 1.6 SR12 or later.
2. In the IBMJavaInstall\jre\lib\security directory, locate the java.security file.
3. In the java.security file, change “keystore.type=jks” to “keystore.type=Windows-MY”.
4. Locate the following content:

Related information
Work Item 156232

JUnit Selenium test scripts cannot be created or saved if the classpath is larger than 1000 characters

First occurrence
6.0.2

Problem
You cannot create or save a JUnit Selenium test script with a classpath larger than 1000 characters.

Steps to reproduce the problem:

1. Browse to Construction > Create test script.
2. Change the test script type to JUnit Selenium.
3. Name the test script and, in the Test Class field, enter the Selenium test class name.
4. In the Classpath field, provide a value that is larger than 1000 characters.
5. Save the test script.

Workaround

Complete the steps for the application server that you use.

IBM WebSphere Application Server

1. Stop the CLM/QM server.
2. Set the system property as follows: “-Dcom.ibm.team.repository.service.internal.RdbRepositoryDataMediator.skipValidationOnSaveItemInTxn=true”. For details about setting the system property, see Setting generic JVM arguments in the WebSphere Application Server V8.5 Liberty profile.
3. Start the CLM/QM server.

Apache Tomcat

1. Stop the CLM/QM server.
2. Set the system property as follows: “-Dcom.ibm.team.repository.service.internal.RdbRepositoryDataMediator.skipValidationOnSaveItemInTxn=true”. For details about setting the system property, see System Properties.
3. Start the CLM/QM server.

Related information
Work Item 154265

Some reports do not open when you click the widget header on the dashboard

First occurrence
6.0.1

Problem
If the Tester Report using Weight or Tester Report using TCER count widgets are added to the dashboard, and you click either widget header to open the report, an error is displayed about a missing report descriptor. Clicking the widget header should open the report page to a detailed view. However, these two reports were deployed with an incorrect report descriptor, which causes the error.

Workaround
Complete these steps to update the report resources with the correct identifier:

1. Go to Reports > Report Resources.
2. Click the Tester Report using Weight report, specify testerWeight.Report for the identifier, and save the report.
3. Click the Tester Report using TCER count report, specify tester.Report for the identifier, specify Tester Report using TER Count for the report name, and save the report.

Related information
Work Item 171987

Work item queries that contain test artifact links cannot be created or edited in the Rational Team Concert Eclipse client

First occurrence
6.0.1

Problem
Work item queries for Task-Review work items that contain test artifact links cannot be created or edited in the Rational Team Concert Eclipse client.

Test artifact links:

• Blocking Test Execution Record
• Related Test Case
• Related Test Script
• Related Test Suite
• Test Case
• Test Plan
• Test Suite
• Test Suite Result
• Test Case Result

Workaround
Create and edit the queries in the Rational Quality Manager web client (https://<host>:<port>/<context root>/console/<project area name>#action=com.ibm.team.workitem.viewWelcome).

Related information
Work Item 141552

In the Reconcile Requirements wizard, filtering for requirements only returns results for requirements on the current page

First occurrence
6.0.1

Problem
When you reconcile requirement collections in test plans and then filter for requirements, the filter returns results for only the requirements that are displayed on the current page.

Workaround
To filter on all available requirements, select one of the following options:

• For Number of Items Per Page, select Display all.
• Manually go through the pages in the table and perform the filter.

Related information
Work Item 140715

Artifacts with the same name can be merged into a single stream when name uniqueness is enabled

First occurrence
6.0

Problem
Rational Quality Manager supports options to enforce name uniqueness for multiple artifact types; however, these options are not honored during a merge across configurations and duplicate names can result.

Workaround
Rename one of the artifacts.

Related information
Work Item 167001

No error is shown when merging configurations fails

First occurrence
6.0

Problem
When you merge configurations, accepting differences from the source configuration can cause an error. However, an error is not shown and the interface stops responding with the merge still in progress.

Workaround
Refresh the browser to try the merge operation again.

Related information
Work item 171049   

Upgrading to a version 6 release causes a data source error in LQE and LDX

First occurrence
6.0

Problem
If you upgrade from any version 5 release of Rational Quality Manager to any version 6 release, the Quality Management data sources in Lifecycle Query Engine (LQE) and Link Index Provider (LDX) are not upgraded and the following error is displayed:

Add data source failed

Workaround
Re-index the Quality Management data sources.

Related information
Work Item 167296

Rational Integration Tester test scripts are not fully executed from test suites

First occurrence
6.0

Problem
If you use a test suite to execute a Rational Integration Tester test script, the execution never finishes and the progress bar stalls at 10% completion. However, you can use a test case to correctly execute the same Rational Integration Tester test script.

Workaround
This issue is a known limitation in Rational Integration Tester 8.7.x that was corrected. Upgrade to Rational Integration Tester 9.0 or later.

Related information
Work Item 147345

Initial Link Index Provider (LDX) indexing fails in large systems when configuration management is enabled

First occurrence
6.0

Problem
When the configuration management capabilities are enabled in a Rational Quality Manager project, Rational DOORS Next Generation uses the Link Index Provider (LDX) to query links between Rational Quality Manager and Rational DOORS Next Generation. The Link Index Provider performs an initial index from the Rational Quality Manager repository when the configuration management capabilities are enabled. If the Rational Quality Manager repository is large, such as more than 1 million test tartifacts, the initial indexing operation can fail because of a timeout error.

Workaround
Complete these steps:

1. As a user who has the JazzAdmin role, log on to Link Index Provider Configuration page: https://<hostname>:<port>/ldx/web/admin/advanced
2. In the Advanced Properties Configuration section, click Edit, and change the value of the Socket Timeout field from 60 to 900 seconds.
3. Go to the Data Sources page, https://<hostname>:<port>/ldx/web/admin/data-sources, click the data source named links_qm, and click Reindex.

If the reindexing operation fails again, wait to allow the Rational Quality Manager Tracked Resource Set (TRS) service to finish the initialization. The Link Index Provider will retry the operation until it succeeds.

Related information
Work Item 136840

Custom attributes with spaces in their names cannot be updated by using the OSLC API

First occurrence
6.0

Problem
You cannot update custom attributes that contain spaces in their names by using the OSLC API. If you try to update a custom attribute that contains spaces, the OSLC API creates a new attribute that contains underscore characters in the name instead of spaces.

Workaround
Rename the original custom attribute and replace any spaces in the name with underscores instead.

Related information
Work Item 170762

Screen capture tool does not work on macOS

First occurrence
5.0.2

Problem
The rich text editor in the web client provides the ability to take screen captures and attach them to artifacts. The screen capture tool is a separate Java application that requires Java Web Start to run. On macOS, if you run the downloaded JNLP file by using Java Web Start with JRE 1.6, 1.7, or 1.8, the following exception occurs: org.eclipse.swt.SWTException: Invalid thread access. This error is caused by a limitation with JNLP, which is a known Java issue.

Workaround
To insert a screen capture in the rich text editor, use the Insert Image toolbar button:

1. Capture an image of the screen by using an external tool.
2. Save the screen capture.
3. Open the Rational Quality Manager rich text editor in the web client.
4. Click the Insert Image toolbar button.
5. In the Insert Image dialog box, click Choose File, and browse to the saved screen capture.
6. Click OK to insert the screen capture in the rich text editor.

Related information
Work Item 161111
Oracle bug JDK-8078230
Oracle bug JDK-8147056

When requirement collection names are updated, the old name is still shown

First occurrence
5.0.2

Problem
This problem occurs when a test plan is associated with a requirement collection and the collection’s name is changed. If you open the test plan, go to the Requirement Collection Links section, and group by Requirement Collection, the old collection name is shown instead of the updated name.

Workaround
Complete these steps:

1. Open the test plan in the test plan editor.
2. Click Requirement Collection Links.
3. Select all of the requirements and click the Reconcile Requirements in Collections icon.

Related information
Work Item 122853

When you export a BIRT report to Microsoft Excel, you cannot open the new file in Excel

First occurrence
5.0.2

Problem
If you export a BIRT report to Microsoft Excel and try to open the new file in Excel, an error message about Problems During Load is shown. The resulting log file mentions XML ERROR in Table. This issue has been observed when reports include both a chart and a table.

Workaround
Open the new file by using Apache OpenOffice Calc.

Related information
Work Item 124705

Requirement names differ between test cases and CSV spreadsheets that are downloaded from them

First occurrence
5.0.2

Problem
When a test case is associated with a requirement and the requirement’s name is changed, if you download the test case as a CSV spreadsheet, the spreadsheet shows the old requirement name.

Workaround
Before you download the test cases as spreadsheets, complete these steps:

1. Remove the requirement link from the test case.
2. Re-add the requirement link to the test case.

Related information
Work Item 121568 

Connection to the mobile client fails when the server has a self-issued SSL certificate that is signed by an internal certificate authority

First occurrence
5.0.1

Problem
When you use the Rational Quality Manager Mobile application, you might have difficulties connecting to the Quality Management server if the certificate that is used in your deployment is internally signed and not from a trusted certificate authority.

Workaround
Follow the detailed guidance on the Jazz.net wiki.

Related information
Work Item 118526

Text in the editor might be displayed in a language that is not installed

First occurrence
5.0

Problem
When you edit an artifact, some context menus, toolbar labels, and tooltips in the editor might be translated into the browser-preferred language even if that language is not selected in IBM Installation Manager during installation. In Rational Quality Manager, you might encounter this issue in these instances:

• In rich text sections of artifacts, such as the Test Case Design, Business Objectives, and Test Suite Design sections
• In custom rich text editor sections
• In the test script editor when you edit steps
• In execution steps when you run a test case execution record

This issue occurs because the editor provides its own language pack. If the matching language version is available, the editor is displayed in the user’s language. If not, the editor is displayed in the default language, which is most commonly English.

Workaround
For consistently translated text in the editor, ensure that you select any required languages in IBM Installation Manager when you install the server. For an existing installation, you can modify the language selection in IBM Installation Manager.

Related information
Work Item 145943

The reconciliation with requirement collections fails with a timeout error

First occurrence
5.0

Problem
This problem occurs only in environments where IBM HTTP Server is configured as a reverse proxy, typically in a cluster environment. In test plans in Rational Quality Manager, the reconciliation with requirement collections fails and responds with a server error. The reconciliation fails after a fixed period of time. In the details of the reconciliation failure, you might see one of two error messages:

• Gateway Time-out The proxy server did not receive a timely response from the upstream server.
• Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request.

Workaround
In the plugin-cfg.xml file, within the <ServerCluster/> tags, set the ServerIOTimeout values to 0 so that the connection will not time out. For more information about the plugin-cfg.xml file, see the “Editing the Web server plugin_cfg.xml file for idle standby” and the “Server cluster” sections in Setting up servers for a basic high-availability configuration.

Related information
Work Item 105153
Reference topic: plugin-cfg.xml file (See the ServerIOTimeout section)
Setting up servers for a basic high-availability configuration

Problems opening the Rational Quality Manager importer from Microsoft Excel or Microsoft Word

First occurrence
5.0

Problem
In Microsoft Excel or Microsoft Word, when you try to open the Rational Quality Manager importer, the expected window might not open. This issue is related to the language setting of the computer. If the language is set to English, the importer works. In other languages, you might notice unexpected behavior, such as the importer window not opening.

Workaround
Complete these steps:

Windows 7 operating systems

1. Open the Control Panel and click Clock, Language, and Region > Change location.
2. Change the format to English (United States).
3. Change the location to United States.

Windows XP operating systems

1. Open the Control Panel and click Regional and Language Options.
2. Change the location to United States.
3. Change the standards and formats to English (United States).

Related information
Work Item 101602

TCERs cannot be generated for a large number of test cases at one time

First occurrence
4.0.5

Problem
If you have a large number of test cases, such as over 500, the following method of generating test case execution records does not work reliably:

1. Browse to Planning > Create test plan.
2. In the Test Cases section, add a large number of test cases (for example, 1000), and save the test plan.
3. Select all the test cases and generate test case execution records.

Workaround
Complete the steps for the application server that you use.

IBM WebSphere Application Server

1. Stop the CLM/QM server.
2. Set the system property as follows: maxParamPerRequest=”1000000″. For details about setting the system property, see Set up system property.
3. Start the CLM/QM server.

Apache Tomcat

1. Stop the CLM/QM server.
2. Set the attribute on the Connector tag of the Server.xml file as follows: maxParameterCount=”1000000″. For details about setting the attribute, see Set connector attribute.
3. Start the CLM/QM server.

Related information
Work Item 139529

Java 7.1 SR4 FP10 is not supported

First occurrence
6.0.5

Problem
Collaborative Lifecycle Management (CLM) applications that run on WebSphere Application Server Liberty (16.0.0.4 and 17.0.0.2) and that are configured with JRE 7.1 SR4 FP10 might crash. By default, versions 6.0.5 and later include a Java version that is stable.

Related information
Work Item 439584

Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for CE/CLM applications on a Windows platform

First occurrence
6.0.5

Problem
Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime.

Related information
Work Item 455371
Work Item 452307
APAR IJ04429

Test suites don’t resume execution after a reconnection between the QM server and command-line adapter

First occurrence
6.0.4

Problem
If you run a test suite that contains multiple command-line adapter scripts, the Quality Management (QM) server might disconnect from and then reconnect to the command-line adapter after a brief period such as 10 minutes. After the reconnection, the test suite execution does not resume running from the previous point. Although the adapter is available and the test suite execution record appears to be in progress, it has stopped responding and is not running. If this situation occurs, you must stop the current test suite execution and start it again.

Related information
Work Item 171757

Test data in a snapshot can change

First occurrence
6.0.2

Problem
When you create a snapshot of a test script, the test data reference in the snapshot is always the same as the current revision of the test script. Therefore, if the current test script changes the reference to the test data, the change is also reflected in all snapshots. Likewise, if the values in the test data change, the changes are reflected in all snapshots. There is no workaround for this issue because the state of the test data is not captured at the time of the snapshot.

Related information
Work Item 148923

Preconditions are not enforced if you run a TCER from an execution schedule

First occurrence
6.0.1

Problem
If you run a test case execution record (TCER) from an execution schedule, the preconditions for the TCER are not enforced. Typically, a TCER cannot run if its preconditions are not met. However, if you add the TCER as a step in an execution schedule and run the TCER from the schedule, the TCER runs even if the preconditions are not met.

Related information
Work Item 171712

RQM Reportable REST API does not support team area process-level operations

First occurrence
6.0.1

Problem
Process and permissions that are defined at the team level do not affect the RQM Reportable REST API behavior. For RQM Reportable REST API operations, all process and permissions operate at the project level only.

Related information
Work Item 140279
Work Item 142815

Test Statistics, Test Matrix, and Execution by Weight dashboard widgets do not display multiple-valued categories correctly

First occurrence
6.0.1

Problem
If you group the Test Statistics, Test Matrix, or Execution by Weight dashboard widgets by a category that has multiple values associated with it, only the results for the first value are displayed. For example, consider a Test Phase category that has three values: Development Test, Integration Test, and User Acceptance Test. The category values are assigned to 7 test cases in the following way:

• 3 test cases have both the Development Test and Integration Test values (the Development Test value is listed first)
• 2 test cases have only the Development Test value
• 2 test cases have only the Integration Test value

In this scenario, the results should show that each value is assigned to 5 test cases. However, because the widgets tabulate only the first value for categories with multiple values, the widgets show that 5 test cases contain the Development Test value, and only 2 test cases contain the Integration Test value.

Related information
Work Item 142093

The “Disallow execution of test case execution record with blocking status” precondition is only enforced from the UI

First occurrence
6.0.1

Problem
The new “Disallow Execution of Test Case Execution Record with Blocking Status” precondition in the project area properties is only enforced when execution is initiated from the UI. When execution is initiated from the utility that uses the Rational Quality Manager Reportable REST API, the precondition is not enforced.

Related information
Work Item 135925
Work Item 142409

Rational Performance Tester cannot connect to the server when Rational Quality Manager is configured with single sign-on (SSO)

First occurrence
6.0

Problem
Rational Performance Tester cannot communicate with the Rational Quality Manager server when Rational Quality Manager is configured with single sign-on (SSO) authentication. When you configure the adapter from Rational Performance Tester and click Connect to RQM, an attempt is made to connect to the Rational Quality Manager server, but the connection is never established. Because the connection does not succeed, the Rational Performance Tester adapter is not listed on the Adapter Console page. A resolution to this issue is available in the Rational Performance Tester 8.7.1 adapter.

Related information
Work Item 137285

Validated By test links from some RM applications to a version 6.0 or later Rational Quality Manager project area that is enabled for configuration management might link to the incorrect test artifact

First occurrence
6.0

Problem
When a version 6.0 or later Rational Quality Manager project area is enabled for configuration management, you cannot create new requirements links to Rational DOORS, Rational DOORS Web Access, or version 5 releases of Rational DOORS Next Generation because these products and versions do not support configuration management. However, you can create a Validated By test link in the opposite direction: from these Requirements Management (RM) applications to a version 6.0 or later Rational Quality Manager project area that is enabled for configuration management. If you create a baseline or stream in the version 6.0 or later Rational Quality Manager project area, the test artifact links that are shown in the RM application might not point to the correct test artifact in the correct configuration. For this reason, you should not create Validated By test links from these RM applications to a version 6.0 or later Rational Quality Manager project area that is enabled for configuration management.

Related information
Work Item 135427

Data Collection Component only loads requirement data from Rational DOORS Next Generation

First occurrence
6.0

Problem
Starting in Rational Quality Manager 6.0, the Data Collection Component only loads requirement data from Rational DOORS Next Generation. The Data Collection Component no longer integrates with applications that are not part of the Rational solution for Collaborative Lifecycle Management (CLM), such as Rational RequisitePro. The Data Collection Component does not load requirement data from such applications or expose it through the Rational Quality Manager Reportable REST API. This limitation also applies to mixed environments that deploy both Rational Quality Manager 5.x and 6.0. This limitation should be considered before upgrading to the Rational solution for CLM version 6.0 or later.

Related information
Work Item 356530   

Guest Access feature is not supported

First occurrence
6.0

Problem
The Guest Access feature enables guest access to secure resources by using a dedicated guest user. However, enabling the Guest Access feature and configuring a Guest Access user ID in the Advanced Properties causes several issues (for example, with browsing and editing test artifacts). Because of these limitations, Guest Access is not supported in Rational Quality Manager.

Related information
Work Item 161061
Work Item 161056
Work Item 161064
Work Item 413189
Work Item 413950

The Rational Quality Manager mobile application does not work in a single sign-on (SSO) environment

First occurrence
6.0

Problem
The Rational Quality Manager mobile application cannot connect to the Rational Quality Manager server when the server is configured for a single sign-on (SSO) environment. In this scenario, you cannot use the mobile application to run tests in offline mode.

Related information
Work Item 137845

Email notifications for formal reviews are not customizable

First occurrence
6.0

Problem
The notification messages that are emailed to users when a formal review on a test artifact changes, such as when an approval or a comment is added, are not customizable. Specifically, on the Manage Project Area page, in the Mail Templates section, any changes to the default text for the following notifications are not included in the email messages that are sent: Approvals, Messages At Me, Work Item Aggregate Changes Notification, and Work Item Changed Notification.

Related information
Work Item 141712

When artifacts are merged from a baseline, some “Accept section” and “Merge section” operations are not supported

First occurrence
6.0

Problem
When you merge artifacts from a baseline, some sections do not support the “Accept section” and “Merge section” operations. To view the support for each artifact type, see the related tables.

Related information
Work Item 138430

Online migration is not supported for upgrading some versions of the Quality Management application

First occurrence
4.0.6

Problem
Online migration for the Quality Management (QM) application is not supported in these upgrade scenarios:

• Upgrading from version 4.0.6 or later to version 4.0.7 or a version 5 release
• Ugrading from a version 5 release to a version 6 release

If you have version 4.0.6 or later of the QM application and perform an online migration before you upgrade to version 4.0.7 or a version 5 release, the operation runs, but no migration occurs. Similarly, if you have a version 5 release and perform an online migration before you upgrade to a version 6 release, the operation runs, but no migration occurs.

Related information
Work Item 361962
Work Item 141120