Red Hat SummitChapter 3. MTA 7.3.0
The MTA 7.3.0 section lists the new features and enhancements, technology preview and developer preview features, fixed issues, and known issues.
3.1. New features
This section provides the new features and improvements of the Migration Toolkit for Applications (MTA) 7.3.0.
Asset generation is available in MTA CLI (Developer Preview)
Starting with MTA 7.3.0, you can run the discover and generate commands in the CLI:
-
The
discovercommand generates the discovery manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. -
The
generatecommand uses the discovery manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for Red Hat OpenShift Container Platform deployments. You can also use the command to generate non-Kubernetes manifests such as a Dockerfile.
(MTA-4610)
MTA uses Red Hat Build of Keycloak for user authentication
MTA 7.3.0 uses the Red Hat Build of Keycloak (RHBK) instance for user authentication and authorization. The MTA Operator manages the RHBK instance and configures a dedicated realm with necessary roles and permissions. For RHBK, the secret and the pod name have changed. The pod name for RHBK is changed to rhbk-operator. (MTA-4540)
CLI flag to list all languages in an application is available (Developer Preview)
In MTA 7.3.0, you can list all languages in an application by using the --list-languages flag in the CLI. The listed language that has no supported providers requires a custom rule set and the --override-provider-settings flag when you analyze the application.
(MTA-4798)
Support for Python and Node.js language providers is available (Technology Preview)
In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available for the application analysis in MTA 7.3.0. As a result, you can now perform the following actions for these providers in the MTA user-interface (UI):
- Add custom migration targets.
- Run custom rules.
(MTA-4542)
3.2. Technology preview features
This section provides a list of all Technology Preview features available in Migration Toolkit for Applications (MTA) 7.3.0.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
Support for Python and Node.js language providers is available
In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available for the application analysis in MTA 7.3.0. As a result, you can now perform the following actions for these providers in the MTA user-interface (UI):
- Add custom migration targets.
- Run custom rules.
(MTA-4542)
3.3. Developer Preview features
This section provides a list of all Developer Preview features available in Migration Toolkit for Applications (MTA) 7.3.0.
For more information about the support scope of Red Hat Developer Preview features, see Developer Preview Features Support Scope.
Asset generation is available in MTA CLI
Starting with MTA 7.3.0, you can run the discover and generate commands in the CLI:
-
The
discovercommand generates the discovery manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest. -
The
generatecommand uses the discovery manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for Red Hat OpenShift Container Platform deployments. You can also use the command to generate non-Kubernetes manifests such as a Dockerfile.
(MTA-4610)
Listing all languages in an application is available
In MTA 7.3.0, you can list all languages in an application by using the --list-languages flag in the CLI. The listed language that has no supported providers requires a custom rule set and the --override-provider-settings flag when you analyze the application.
(MTA-4798)
3.4. Fixed issues
This section provides the following bug fixes and resolves issues and other problems that have a significant impact on the Migration Toolkit for Applications (MTA) 7.3.0.
MTA CLI now excludes the target folder when analyzing compiled Java Maven projects
Previously, for compiled Java Maven projects, the MTA CLI included incidents by analyzing the target folder. This generated different reports for Java Maven projects before and after running the mvn-clean-package command. This issue has been resolved in MTA 7.3.0. (MTA-5078)
Application credential update now triggers a new discovery task
Previously, when you updated the source or Maven credential for an application, a new discovery task was not triggered in the MTA user interface. This issue has been resolved in MTA 7.3.0. (MTA-5121)
3.5. Known issues
This section provides highlighted known issues in Migration Toolkit for Applications (MTA) version 7.3.0.
.NET Framework application analysis fails in the MTA CLI
When you analyze .NET Framework applications in Windows containers by using the MTA CLI, the analysis fails for the following environment variables:
-
DOTNET_PROVIDER_IMG:quay.io/konveyor/dotnet-external-provider:release-0.7 -
RUNNER_IMG:quay.io/konveyor/kantra:latest -
PODMAN_BIN:C:\Program Files\Docker\Docker\resources\bin\docker.exe
Workaround: Use the following version of the Dotnet provider image: set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0
Non-Java applications are analyzed in containerless mode in the MTA CLI
When you analyze non-Java applications, MTA initiates the analysis in containerless mode.
Workaround: set the --run-local=false flag to analyze non-Java applications. (MTA-5068)
Application analysis fails to get a list of dependencies for Node.js in the MTA UI
When you run an application analysis for the Node.js language provider by using the MTA user-interface (UI), the analysis completes with the following error displayed in the analysis log:
level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
Workaround: Set the Analysis Mode setting to source-only.
The Node.js provider does not have a dependency capability. Therefore, a dependency list cannot be generated. The same applies for the Python provider.
(MTA-5070)
Dependency rule of a custom rules file in analysis is not fired
A custom dependency rule is not fired, and no related migration issue is found. (MTA-3863)
No multi-user access restrictions on resources
An analyzer task does not have multi-user access restrictions on resources. For example, an analyzer task created by a user can be canceled by any other user. (MTA-3819)
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}