-
Bug
-
Resolution: Done-Errata
-
Major
-
MTA 7.0.0
-
None
-
None
-
False
-
-
False
-
-
-
No
Description of problem:
Analysis on Nexus or OpenMRS app source code with target OpenJDK (no matter the version) is failing.
Version-Release number of selected component (if applicable): 7.0.0
How reproducible: Always
Steps to Reproduce:
1. Create an application, providing one of the following repositories: https://github.com/sonatype/nexus-public | https://github.com/openmrs/openmrs-core
2. Perform an analysis on that application selecting OpenJDK as the target
Actual results:
The analysis fails (details attached)
Expected results:
The analysis should complete successfully
Additional info:
Analysis details and Pod logs can be found attached to this Bug.
- links to
-
RHBA-2023:120350
Migration Toolkit for Applications bug fix and enhancement update
- mentioned on
[MTA-1647] Analysis for Nexus and OpenMRS source code fails
This issue is no longer reproducible on MTA 7.0.0-48, thanks!
GitLab CEE Bot
added a comment - CPaaS Service Account mentioned this issue in a merge request of rhmt / MTA Midstream on branch mta-7.0-rhel-9_upstream_5bd788235f42d0b9fc5fa1c96bcfc741:
Updated 6 upstream sources
GitLab CEE Bot
added a comment - CPaaS Service Account mentioned this issue in a merge request of rhmt / MTA Midstream on branch mta-7.0-rhel-9_ upstream _5bd788235f42d0b9fc5fa1c96bcfc741 : Updated 6 upstream sources https://github.com/konveyor/tackle2-hub/pull/573
Updated the hub API to de-duplicate dependencies with preference for direct.
Jeff Ortel
added a comment - - edited https://github.com/konveyor/tackle2-hub/pull/573
Updated the hub API to de-duplicate dependencies with preference for direct. 
Dylan Murray
added a comment - https://github.com/konveyor/analyzer-lsp/pull/444
This fixes some issues with openmrs, but not the 409 error
Dylan Murray
added a comment - https://github.com/konveyor/analyzer-lsp/pull/444
This fixes some issues with openmrs, but not the 409 error Dylan Murray
added a comment - I just tested this on build 46 and saw the following errors (see attached)1699552589668.yaml
Dylan Murray
added a comment - I just tested this on build 46 and saw the following errors (see attached) 1699552589668.yaml Jeff Ortel
added a comment - The addon will not POST the analysis when the analyzer crashes.
The 409 would (n this case) indicate a duplicate dependency reported.
Jeff Ortel
added a comment - The addon will not POST the analysis when the analyzer crashes.
The 409 would (n this case) indicate a duplicate dependency reported. 
Fabian von Feilitzsch (Inactive)
added a comment - The 409 is surprising, jortel if the analyzer crashes could it lead to that somehow? I see an unexpected panic in the analyzer log, could be a separate issue though. Will dig into it
Fabian von Feilitzsch (Inactive)
added a comment - The 409 is surprising, jortel if the analyzer crashes could it lead to that somehow? I see an unexpected panic in the analyzer log, could be a separate issue though. Will dig into it Dylan Murray
added a comment - Thank you rh-ee-abrugaro that is a new one... will look into it. I tested it in MTA 7.0.0-46 and both analyses keep failing for me, but looks like the previous error is fixed and now they're failing for a different reason:
errors:
- severity: Error
description: 'POST /applications/1/analyses failed: 409(Conflict) body: {"error":"UNIQUE constraint failed: TechDependency.Provider,TechDependency.Name,TechDependency.Version,TechDependency.SHA,TechDependency.AnalysisID"}' - severity: Error
description: 'Pod failed: Error'
activity:
I attached the analysis details for the nexus analysis but both are failing for the same reason.
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Migration Toolkit for Applications bug fix and enhancement update), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2024:0599