Skip to content

Commit d16e7ce

Browse files
author
Prabha Kylasamiyer Sundara Rajan
committed
MTA-4810 Release Notes for 7.3.1
modified: docs/release-notes/master.adoc new file: docs/topics/ref_fixed-issues-7-3-1.adoc
1 parent 441ee69 commit d16e7ce

File tree

4 files changed

+106
-28
lines changed

4 files changed

+106
-28
lines changed

docs/release-notes/master.adoc

Lines changed: 10 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,15 @@ include::topics/making-open-source-more-inclusive.adoc[]
1818

1919
{ProductFullName} {DocInfoProductNumber} accelerates large-scale application modernization efforts across hybrid cloud environments on {ocp-first}. 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 {ocp-short} through the user interface (UI) and command-line interface (CLI).
2020

21+
[id="mta-7-3-1"]
22+
== {ProductShortName} 7.3.1
23+
24+
include::topics/ref_new-features-7-3-1.adoc[leveloffset=+2]
25+
26+
include::topics/ref_fixed-issues-7-3-1.adoc[leveloffset=+2]
27+
28+
include::topics/ref_known-issues-7-3-1.adoc[leveloffset=+2]
29+
2130
[id="mta-7-3-0"]
2231
== {ProductShortName} 7.3.0
2332

@@ -27,41 +36,14 @@ include::topics/ref_fixed-issues-7-3-0.adoc[leveloffset=+2]
2736

2837
include::topics/ref_known-issues-7-3-0.adoc[leveloffset=+2]
2938

30-
31-
[id="mta-7-2-2"]
32-
== {ProductShortName} 7.2.2
33-
34-
include::topics/ref_resolved-issues-7-2-2.adoc[leveloffset=+2]
35-
36-
include::topics/ref_known-issues-7-2-2.adoc[leveloffset=+2]
37-
38-
[id="mta-7-2-1"]
39-
== {ProductShortName} 7.2.1
40-
41-
include::topics/ref_resolved-issues-7-2-1.adoc[leveloffset=+2]
42-
43-
include::topics/ref_known-issues-7-2-1.adoc[leveloffset=+2]
44-
45-
46-
[id="mta-7-2-0"]
47-
== {ProductShortName} 7.2.0
48-
49-
include::topics/ref_new-features-7-2-0.adoc[leveloffset=+2]
50-
51-
// include::topics/ref_upgrade-notes-7-2-0.adoc[leveloffset=+2]
52-
53-
include::topics/ref_resolved-issues-7-2-0.adoc[leveloffset=+2]
54-
55-
include::topics/ref_known-issues-7-2-0.adoc[leveloffset=+2]
56-
5739
//snippets required for release notes and other locations
5840
include::topics/analysis-dependency-rule-snippet.adoc[]
5941

6042
include::topics/analyzer-rbac-known-issue-snippet.adoc[]
6143

6244
// include::topics/svn-checkout-fails-issue-snippet.adoc[]
6345

64-
For a complete list of all known issues, see the list of link:https://issues.redhat.com/issues/?filter=12447880[{ProductShortName} 7.2.0 known issues] in Jira.
46+
For a complete list of all known issues, see the list of link:https://issues.redhat.com/issues/?filter=12469170[{ProductShortName} 7.3.1 known issues] in Jira.
6547

6648

6749
:!release-notes:
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
:_newdoc-version: 2.18.3
2+
:_template-generated: 2025-05-12
3+
4+
:_mod-docs-content-type: REFERENCE
5+
6+
[id="fixed-issues-7-3-1_{context}"]
7+
= Fixed issues
8+
9+
This section provides the following bug fixes and resolved issues and other problems that have a significant impact on the {ProductFullName} 7.3.1.
10+
11+
.{ProductShortName} reports generated after a {CLIName} analysis now display the issue description
12+
Previously, after running an analysis in the {CLIName}, {ProductShortName} incorrectly displayed the incident message with the issue description for issues listed in the static report. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5293[(MTA-5293)]
13+
14+
.{ProductShortName} {WebName} now completes application analysis in clusters with low resources
15+
Previously, when you ran containerized application analysis in a cluster with slower disk I/O or low storage, the technology discovery took longer and the analysis failed because the rule execution timed out with the error `unable to ask for Konveyor rule entry`. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5369[(MTA-5369)]
16+
17+
.Custom rules are now triggered for applications without the `pom` file
18+
Previously, {ProductShortName} did not trigger custom rules for applications without the `pom` file. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5049[MTA-5049]
19+
20+
.{ProductShortName} now triggers custom rules for application analysis
21+
Previously, {ProductShortName} did not trigger custom rules when analyzing applications. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-4885[(MTA-4885)]
22+
23+
.{ProductShortName} now analyzes Java applications without false positives
24+
Previously, {ProductShortName} sometimes generated a false positive by matching `line 1` of a Java file. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-4918[(MTA-4918)]
25+
26+
.{ProductShortName} {CLIName} analysis is now optimized for multi-module binaries with dependencies
27+
Previously, when you analyzed multi-module binaries in the {ProductShortName} {CLIName}, the analysis could take a long time to complete if dependency resolution failed. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5398[(MTA-5398)]
28+
29+
.{ProductShortName} {CLIName} now allows disabling dependency rules for analysis
30+
Previously, {ProductShortName} {CLIName} ran dependency rules during application analysis without an option to skip such rules. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5399[(MTA-5399)]
31+
32+
.{ProductShortName} {WebName} now allows the SSH URL of a Git repository as a source
33+
Previously, {ProductShortName} {WebName} did not permit you to enter the SSH URL of a Git repository as the source application. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5385[(MTA-5385)]
34+
35+
.{ProductShortName} {WebName} now creates a Tackle custom resource that requires authentication
36+
Previously in {ProductShortName} {WebName}, creation of Tackle CR with the `feature_auth_required` field set to `true` failed. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5386[(MTA-5386)]
37+
38+
.{ProductShortName} now runs Java rules when analyzing Java binaries in Windows
39+
Previously, when you performed a containerless analysis of compiled Java applications in Windows, {ProductShortName} did not match a Java rule and generated a Java Model (code 969) error. As a result, some rules did not trigger issues in the analysis report. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5427[(MTA-5427)]
40+
41+
.{ProductShortName} {CLIName} now analyzes non-Java applications in containerized mode
42+
Previously, when you analyzed non-Java applications, {ProductShortName} initiated the analysis in containerless mode. This issue has been resolved in {ProductShortName} 7.3.1. link:https://issues.redhat.com/browse/MTA-5068[(MTA-5068)]
43+
44+
.Resources limits and requests are now present on all pods
45+
Previously in {ProductShortName} 7.3.1, all pods created by the `mta-operator` and the pod for the operator have resource limits and requests set. This way they also work in an environment where resource limits and requests are required, for example, when a project has resource quotas defined. link:https://issues.redhat.com/browse/MTA-5426[(MTA-5426)]
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
:_newdoc-version: 2.18.3
2+
:_template-generated: 2025-04-29
3+
4+
:_mod-docs-content-type: REFERENCE
5+
6+
[id="known-issues-7-3-1_{context}"]
7+
= Known issues
8+
9+
This section provides highlighted known issues in {ProductFullName} version 7.3.1.
10+
11+
.Running analysis on large `.EAR` binary files obtains differents results
12+
13+
When analyzing binary applications, {ProductShortName} relies on the Maven search index to determine whether dependencies are internal to the application or whether the application is installed as an open-source dependency. Depending on the availability of the Maven search index, it is assumed that an open-source dependency is internal to the application and includes the dependency in the analysis results. In this case, analysis returns more incidents and greater effort to address issues found in dependencies, even if the user does not expect to see those results. link:https://issues.redhat.com/browse/MTA-5588[(MTA-5588)]
14+
15+
.{ProductShortName} {CLIName} generates a process error in log after Java binary analysis in Windows
16+
When you analyze Java binaries in Windows, {ProductShortName} {CLIName} generates a process error when deleting files in the `exploded` directory after moving the decompiled files to the Java project path. This error does not affect the analysis results. Currently, there is no workaround for this issue. link:https://issues.redhat.com/browse/MTA-5355[(MTA-5355)]
17+
18+
.{ProductShortName} {CLIName} does not detect dependencies for Gradle projects
19+
When you analyze Gradle projects in containerless mode, the {ProductShortName} {CLIName} does not detect dependencies during analysis. link:https://issues.redhat.com/browse/MTA-4033[(MTA-4033)]
20+
21+
.{ProductShortName} {WebName} static reports do not display rule description in incidents
22+
In incidents that are found in the static report after analysis, {ProductShortName} {WebName} does not describe the rule that triggered the incident. link:https://issues.redhat.com/browse/MTA-5643[(MTA-5643)]
23+
24+
.`.NET` Framework application analysis fails in the {ProductShortName} {CLIName}
25+
26+
When you analyze `.NET` Framework applications in Windows containers by using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables:
27+
28+
`DOTNET_PROVIDER_IMG`: `quay.io/konveyor/dotnet-external-provider:release-0.7`
29+
30+
`RUNNER_IMG`: `quay.io/konveyor/kantra:latest`
31+
32+
`PODMAN_BIN`: `C:\Program Files\Docker\Docker\resources\bin\docker.exe`
33+
34+
Workaround: Use the following version of the Dotnet provider image:
35+
36+
`set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0` link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
:_newdoc-version: 2.18.3
2+
:_template-generated: 2025-04-17
3+
4+
:_mod-docs-content-type: REFERENCE
5+
6+
[id="new-features-7-3-1_{context}"]
7+
= New features
8+
9+
This section provides the new features and improvements of the {ProductFullName} 7.3.1.
10+
11+
.FIPS is now supported in {ProductShortName}
12+
13+
Federal Information Processing Standards (FIPS) are a set of computer security standards developed by the United States federal government in line with the Federal Information Security Management Act (FISMA).
14+
15+
{ProductFullName} has been tested and works on FIPS-enabled {ProductShortName} clusters.

0 commit comments

Comments
 (0)