Chapter 3. MTA 7-0-2
3.1. New features
This section describes the new features and improvements of the Migration Toolkit for Applications (MTA) 7.0.2.
Multiarch support for MTA CLI introduced
In MTA 7.0.2, multiarch support for for MTA CLI is introduced. Multiarch support includes both ARM architecture on Linux machines and Apple Silicon Macs.
3.2. Known issues
Migration Toolkit for Applications (MTA) version 7.0.2 has the following known issues.
Failure to connect to Jira server using basic authentication
In MTA 7.0.2, connecting to a Jira server using basic authentication, meaning username and password, fails. This issue is scheduled to be resolved in MTA 7.1.0. (MTA-2427)
Unable to turn on Enable insecure communication switch
In MTA 7.0.2, it is not possible to turn on the Enable insecure communication switch when creating or editing a Jira instance. This issue is scheduled to be resolved in MTA 7.0.3. (MTA-2426)
Unable to run analysis on a directory of multiple applications
MTA 7.0.2 and 7.0.3 fails to run analysis on a directory of multiple applications. The cause of this failure is caused as the analyzer is expecting a pom.xml file in the root directory. (MTA-2765)
For a complete list of all known issues in this release, see the list of Known Issues in Jira.
3.2.1. CLI known issues
Limitations with Podman on Microsoft Windows
The CLI is built and distributed with support for Microsoft Windows.
However, when running any container image based on Red Hat Enterprise Linux 9 (RHEL9) or Universal Base Image 9 (UBI9), the following error can be returned when starting the container:
Fatal glibc error: CPU does not support x86-64-v2
This error is caused because Red Hat Enterprise Linux 9 or Universal Base Image 9 container images must be run on a CPU architecture that supports x86-64-v2.
For more details, see (Running Red Hat Enterprise Linux 9 (RHEL) or Universal Base Image (UBI) 9 container images fail with "Fatal glibc error: CPU does not support x86-64-v2").
CLI runs the container runtime correctly. However, different container runtime configurations are not supported.
Although unsupported, you can run CLI with Docker instead of Podman, which would resolve this issue.
To achieve this, you replace the PODMAN_BIN path with the path to Docker.
For example, if you experience this issue, instead of issuing:
PODMAN_BIN=/usr/local/bin/docker mta-cli analyze
You replace PODMAN_BIN with the path to Docker:
<Docker Root Dir>=/usr/local/bin/docker mta-cli analyze
While this is not supported, it would allow you to explore CLI while you work to upgrade your hardware or move to hardware that supports x86_64-v2.
3.3. Resolved issues
The following highlighted issues have been resolved in Migration Toolkit for Applications (MTA) version 7.0.2.
CVE-2022-1962: Golang: go/parser stack exhaustion in all Parse* functions Security
A flaw was found in versions of the Golang standard library go/parser, before Go 1.17.12 and Go 1.18.4. When calling any Parse functions on the Go source code, which contains deeply nested types or declarations, a panic can occur due to stack exhaustion. This issue allows an attacker to impact system availability.
For more details, see (CVE-2022-1962).
MTA CLI does not function as expected on ARM-based machines
In previous versions of MTA 7.0, there was an issue with the Command-line interface (CLI) not functioning as expected on ARM CPU architecture.
- MTA CLI does not work on Mac ARM-based machines. (MTA-2160)
- MTA CLI does not work on Linux ARM-based machines. (MTA-2351)
These issues have been resolved in MTA 7.0.2.
Missing text below graphs on the Reports page
In previous versions of MTA 7.0, the text below graphs was missing on the Reports page. This has been resolved in MTA 7.0.2. (MTA-1868)
Assessment status is In progress instead of Not started
In previous versions of MTA 7.0, the Assessment status was In progress instead of Not started when the application was associated with an archived questionnaire. This has been resolved in MTA 7.0.2. (MTA-1956)
Turning off Use Refresh Tokens breaks MTA UI
In previous versions of MTA, turning off the Use Refresh Tokens, which is a feature in the Red Hat build of Keycloak, could have adversely impacted MTA. This has been resolved in MTA 7.0.2. (MTA-1255)
Exporting a questionnaire includes unnecessary metadata
In previous versions of MTA 7.0, exporting a questionnaire could include unnecessary metadata. This unnecessary metadata had the potential to make reimporting the questionnaire a more difficult task, as it might conflict with already existing data. This has been resolved in MTA 7.0.2, with exports not including any environment-specific data. (MTA-1721)
Source and dependency analysis of applications built with JDKs before 11 fails compilation
In previous versions of MTA, source and dependency analysis of applications built with Java Development Kits (JDKs) earlier than version 11 could fail before compilation was completed. This has been resolved in MTA 7.0.2. (MTA-1785)
Application drawer incorrectly lists assessed archetypes when there are no required questionnaires
In previous versions of MTA 7.0, the application drawer incorrectly showed that the associated archetypes had been assessed, when there were no required questionnaires and when an application was associated with unassessed archetypes. This has been resolved in MTA 7.0.2. (MTA-1967)
Inherited assessment tags should be listed as assessment tags instead of archetype tags on the app drawer
In previous versions of MTA 7.0, inherited assessment tags should have been listed as assessment tags instead of archetype tags on the app drawer. This has been resolved in MTA 7.0.2. (MTA-1972)
Application Assessment status shows Completed instead of Not started for inherited assessment after the questionnaire is archived
In previous versions of MTA 7.0, the Application Assessment status showed Completed instead of Not started for inherited assessment after the questionnaire was archived. This has been resolved in MTA 7.0.2. (MTA-1973)
Application inventory page shows no applications after accessing dependencies
In previous versions of MTA 7.0, the Application inventory page showed no applications after accessing dependencies. This has been resolved in MTA 7.0.2. (MTA-2007)
Dependencies does not filter and navigate to the affected applications
In previous versions of MTA 7.0, dependencies did not filter and navigate to the affected applications, instead of showing only the affected applications. This has been resolved in MTA 7.0.2. (MTA-2008)
Analyzer unable to connect message seen on the Single Application issues page
In previous versions of MTA 7.0, on an analysis clicking on Issues and then navigating to the Single application page, no data was shown and an Unable to connect message was shown. There was an error retrieving data, showing a Check your connection and try again error. This has been resolved in MTA 7.0.2. (MTA-2047)
Issues contain variable names instead of values
In previous versions of MTA 7.0, issues occasionally contained variable names instead of values. This has been resolved in MTA 7.0.2. (MTA-2067)
Rules from technology usage appear as issues
In previous versions of MTA 7.0, rules from technology usage appeared as issues. This has been resolved in MTA 7.0.2. (MTA-2099)
MTA CLI does not have a version flag
In previous versions of MTA 7.0, there was no version flag for the MTA CLI, such as mta-cli --version to show the current version installed. This has been resolved in MTA 7.0.2. (MTA-2201)
Application list in the Archetype side drawer does not scale well
In previous versions of MTA 7.0, the Application list in the Archetype side drawer did not scale well when a large number of applications were associated with the archetype. It is likely that a massive number of applications could cause the drawer not to load properly. This has been resolved in MTA 7.0.2. (MTA-2283)
For a complete list of all issues resolved in this release, see the list of Resolved Issues in Jira.
3.4. Upgrade notes
The following are upgrade notes for Migration Toolkit for Applications (MTA)
Upgrade from MTA 6.2.1 to MTA 7.0.2
Upgrade directly from MTA 6.2.1 to MTA 7.0.2.
Pathfinder assessment migration fails on upgrade from MTA 6.2.1 to MTA 7.0.0
In previous version of MTA 7.0.0, when MTA 6.2.1 is installed, and you attempt to switch the channel to stable-7.0, the operator upgrade succeeds, but a task in the operator pod fails. This failure resulted in existing pathfinder assessments not being migrated to MTA 7.0.0. As this bug has been resolved in MTA 7.0.1, it is suggested to upgrade directly from MTA 6.2.1 to MTA 7.0.2. MTA-2139
On upgrading from MTA 6.2.1 to MTA 7.0.1 , completed assessment are shown as In progress. Enable the legacy Pathfinder questionnaire to see the completed status of assessment.
Hub database volume size
In version 7.0.2 of MTA, the default size of the hub database volume has been increased to 10GiB.
If your storage class does not support volume expansion, then an upgrade from 6.2.1 to 7.0.2 will result in a failure due to the operator trying to change the volume size from 5GiB to 10GiB.
To avoid this issue, you can directly set the volume size by setting:
... hub_database_volume_size: 5Gi ...
By doing this, you will avoid the operator trying to resize the volume.
If this value was set when the previous version was deployed, there is no need to take any action, as it will work as expected.
Existing data
When upgrading to MTA 7.0.0, all existing data will be retained, except for individual analysis reports for applications.
As both the analysis and reporting engines have been replaced with this version, you will be required to conduct a re-run of the analysis in order to obtain data on issues and dependencies.
