Closed dymurray closed 1 month ago
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.
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
Retesting on the same environment and this is not 100% reproducible any longer, in fact I'm unable to reproduce it right now.
Reproducer scenarios:
deps.yaml
is not created, and when it does get createdNOT reproducible in v0.5.0
Is there an existing issue for this?
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
openjdk21
Environment
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 inpending
forever. Check the hub pod logs to see the unique constraint error.