[BUG] Analysis of application with is causing applications to disappear due to deadlock

[dymurray]

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

latest

Priority

Blocker

Current Behavior

Running analysis is leading to errors in the hub about a Unique Constraint being violated and then causes the application inventory to be empty. There are also errors about deps.yaml not existing.

Expected Behavior

Analysis should succeed.

How Reproducible

Always (Default)

Steps To Reproduce

1. Create application for https://github.com/kissaten/gradle-multi-project-example
2. Analyze source only with target of openjdk21
3. Add custom rule:

- category: mandatory
  description: |
    This rule looks for a given annotation used with another annotation
  message: "Annotation instpection 05"
  ruleID: java-annotation-inspection-05
  labels:
  - konveyor.io/target=openjdk21
  when:
    java.referenced:
      pattern: org.springframework.context.annotation.Configuration
      location: ANNOTATION
      annotated:
        pattern: org.springframework.data.jpa.repository.config.EnableJpaRepositories
        elements:
          - name: basePackages
            value: "io.konveyor.demo.ordermanagement.repository"

- category: mandatory
  customVariables: []
  description: MicroProfile Metrics not supported
  effort: 1
  labels:
  - konveyor.io/target=openjdk21
  - JBossEAP
  - EAPXP
  links: []
  message: If you migrate your application to JBoss EAP XP 5.0 (or later), please
    note that MicroProfile Metrics is not supported.
  ruleID: gradle-sample-rule
  when:
    java.referenced:
      pattern: com.sun.net.httpserver.HttpServer
      location: IMPORT

4. Run analysis

Environment

- OS:

Anything else?

tackle-hub-7879cc4ff9-75dct-tackle-hub.log

task-7-v2cks-addon.log

Check the task logs to see the deps.yaml error. Check the screenshot to see the UI network requests sit in pending forever. Check the hub pod logs to see the unique constraint error.

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[dymurray]

Deleting the hub pod causes the UI to resolve itself and the applications come back into the inventory. The associated analysis actually fails with the following details
log-merged-7.json

[dymurray]

Retesting on the same environment and this is not 100% reproducible any longer, in fact I'm unable to reproduce it right now.

[dymurray]

Reproducer scenarios:

• Gradle app and https://github.com/WASdev/sample.DefaultApplication/tree/main -> source only & source+deps
• When deps.yaml is not created, and when it does get created

NOT reproducible in v0.5.0