Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Including Camel target in analysis of tackle-testapp-public causes other issues to disappear #650

Open
1 task done
mansam opened this issue Jul 11, 2024 · 1 comment
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@mansam
Copy link

mansam commented Jul 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

0.5.0-beta.1

Priority

Critical

Current Behavior

Including the Camel target with any other combination of targets (including all of them) while running an analysis seems to cause no issues to be reported for an analysis that would otherwise report issues, with the exception of issues related to the Azure target. This is consistently reproducible.

The analysis report includes the following error messages when the Camel target is included:

errors:
    - severity: Error
      description: '[Analyzer] camel3/camel2.component-changes-00010: could not parse provided xpath query ''//*[c:crypto and not(b:crypto/@algorithm)]/c:crypto'': prefix b not defined.'
    - severity: Error
      description: '[Analyzer] camel3/camel2.component-changes-00010: could not parse provided xpath query ''//*[c:crypto and not(b:crypto/@algorithm)]/c:crypto'': prefix b not defined.'
    - severity: Error
      description: '[Analyzer] camel3/camel2.component-changes-00011: could not parse provided xpath query ''//*[c:secureXML and (count(c:secureXML/@passPhrase)+count(c:secureXML/@passPhraseByte))<1]/c:secureXML/'': expression must evaluate to a node-set'

Expected Behavior

Adding more targets should not cause less issues to be reported.

How Reproducible

Always (Default)

Steps To Reproduce

Case 1:

  1. Add tackle-testapp-public to application inventory.
  2. Run analysis, selecting Quarkus target.
  3. Observe that there are several Quarkus issues reported.

Case 2:

  1. Add tackle-testapp-public to application inventory.
  2. Run analysis, selecting Quarkus and Camel targets.
  3. Observe that there are no issues reported.

Case 3:

  1. Add tackle-testapp-public to application inventory.
  2. Run analysis, selecting Quarkus, Camel and Azure targets.
  3. Observe that there is one issue reported, related to the Azure target.

Environment

No response

Anything else?

report.txt

@mansam mansam added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 11, 2024
@mansam mansam added this to Planning Jul 11, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Jul 11, 2024
@konveyor-ci-bot
Copy link

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.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Jul 11, 2024
@dymurray dymurray added this to the v0.5.0 milestone Jul 15, 2024
@dymurray dymurray added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 15, 2024
@dymurray dymurray moved this from 🆕 New to 🔖 Ready in Planning Jul 15, 2024
@konveyor-ci-bot konveyor-ci-bot bot removed the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Jul 15, 2024
@dymurray dymurray modified the milestones: v0.5.0, v0.5.1 Jul 18, 2024
@dymurray dymurray added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Status: 🔖 Ready
Development

No branches or pull requests

3 participants