Release Notes
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
1. Introduction
Migration Toolkit for Applications 6.2 accelerates large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface.
These release notes cover all z-stream releases of MTA 6.2 with the most recent release listed first.
2. MTA 6.2.0
2.1. New features
This section describes the new features of the Migration Toolkit for Applications (MTA) 6.2.0.
The integration of Migration Toolkit for Applications with Jira allows you to track and manage the whole migration process. To introduce changes to the applications in the portfolio, you can create issues in Jira and assign them to developers.
For more information, see Creating and configuring a Jira connection.
A migration wave is a small collection of workloads that deliver business value. MTA’s Migration Wave groups applications to be migrated on a specified schedule.
In addition, a migration wave enables you to export a list of the wave’s applications to the Jira issue management system. This automatically creates a separate Jira issue for each application of the migration wave for tracking.
For more information, see Creating migration waves and Creating Jira issues for a migration wave.
MTA integrates with OpenShift Monitoring, which allows Red Hat to collect data that will display usage of MTA in the field by customers, beyond installation.
2.2. Known issues
MTA version 6.2.0 has the following issues.
Keycloak is enabled by default. If you disable and then re-enable Keycloak, you cannot perform any actions in the MTA web console after logging in again.
This error is caused as the credential-mta-rhsso secret is updated when auth/Keycloak is disabled and re-enabled.
The suggested workaround is to restore the old password in the credential-mta-rhsso secret, after re-enabling auth. MTA-1152
When fetching custom rules from a repository during an analysis, if the Root path field contains spaces, the mta-cli command is not properly composed and the analysis fails. MTA-458
Update notifications are disabled for Application, Job function and Business services, as a result, no notifications are displayed. MTA-1024
The Repository type field is not required when saving the configuring rules files from a repository in analysis. MTA-1047
When creating a new Jira instance, the connection status is initially shown as Not connected before it moves to Connected, and this delay could cause the user to think that the provided credentials are incorrect. MTA-1019
For a complete list of all known issues in this release, see the list of Known Issues in Jira.
2.3. Resolved issues
The following highlighted issues have been resolved in MTA version 6.2.0.
The release of MTA 6.2.0 resolves the issue that Analysis wizard was stuck on the custom rules page on moving Back from the Repository tab. For more information on this issue, see MTA-464.
The release of MTA 6.2.0 resolves the issue that an analysis was running for an application, and after clicking on that application to see the Tags and Reports, both the tabs keep loading until the analysis finished. For more information on this issue, see MTA-465.
For a complete list of all issues resolved in this release, see the list of Resolved Issues in Jira.