Description of problem:
Containerless analysis results with report missing issues comparing to container analysis when using maven settings file
Version-Release number of selected component (if applicable):
7.2.2-10
How reproducible:
100%
Steps to Reproduce:
1. Run local analysis like
/home/igor/.kantra/mta-cli analyze --overwrite --input /home/igor/github.com/kantra-cli-tests/data/applications/tackle-testapp-public --output /home/igor/MTA/reports-automation --target cloud-readiness--maven-settings /home/igor/github.com/kantra-cli-tests/data/xml/tackle-testapp-public-settings.xml
2. Run same analysis in container (add --run-local=false at the end)
3. Compare resulting reports
Actual results:
Reports will be different, local analysis report will miss some issues
Expected results:
Results should be equal
Additional info:
Problem doesn't reproduce on Mac, only Linux and Windows are affected
- relates to
-
MTA-4887 [DOC] [CLI guide] Ensure that JDK requirements for Linux indicate to install Development package
-
- Testing
-
- links to
-
RHBA-2025:146602
Migration Toolkit for Applications bug fix and enhancement update
[MTA-4811] [Containerless CLI] [Linux] Report is missing issues comparing to container analysis when using maven settings file
build 7.2.2-17 doesn't reproduce this problem in Windows 10/11 and Mac amd64, I assume this problem is Linux-specific emcmulla@redhat.com
Hi emcmulla@redhat.com , just reproduced this on Linux. Ran 2 commands:
Local analysis:
/home/igor/.kantra/mta-cli analyze --overwrite --input /home/igor/github.com/kantra-cli-tests/data/applications/tackle-testapp-public --output /home/igor/MTA/reports-maven-local --target cloud-readiness --maven-settings /home/igor/.secrets/tackle-testapp-public-settings.xml
and container analysis:
/home/igor/.kantra/mta-cli analyze --overwrite --input /home/igor/github.com/kantra-cli-tests/data/applications/tackle-testapp-public --output /home/igor/MTA/reports-maven-container --target cloud-readiness --maven-settings /home/igor/.secrets/tackle-testapp-public-settings.xml --run-local=false
As you can see, there are only 2 differences in commands: 1 is for making a container run and second is path where report should be saved.
Please find both reports attached, they are different and local run is missing one of 2 issues.
Also I am going to reproduce this on Windows as well.
ibragins@redhat.com I can't reproduce this on this build with Windows (don't have access to Linux). Is it the `local-storage-00001` rule that is missing? It could be that on Mac, you already have that matching dep in your M2 cache, so the maven settings file isn't needed there for it. But if you do not have it in your windows/linux envs, and your maven settings creds aren't valid, it makes sense that that rule is missing.
I'd check for the matching file from the missing rule in your M2 cache after running analysis. I believe it's at `HOME/.m2/repo/io/konveyor/demo/configuration-utils/1.0.0/io/konveyor/demo/config/ApplicationConfiguration.java`
If that path doesn't exist, your maven settings file may have an issue.
ibragins@redhat.com,
Is this a regression compared to previous MTA 7.2.1?
Closing this bug as not a bug since this issue was due to a missing OpenJDK development tools install on a Linux setup.
ibragins@redhat.com,
Please add a doc task to document this Linux specific requirement to MTA Docs and link it to this bug.