Uploaded image for project: 'Migration Toolkit for Applications'
  1. Migration Toolkit for Applications
  2. MTA-4772

[CLI] No respective issues are triggered when custom rule was applied

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • MTA 7.2.2
    • MTA 7.3.0
    • MTA CLI
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      Description of problem:

      No respective issues are triggered when custom rule was applied

      Version-Release number of selected component (if applicable):

      7.3.0-8

      How reproducible:

      100%

      Steps to Reproduce:
      1. Run command like

      /home/igor/.kantra/mta-cli analyze --overwrite --input /home/igor/github.com/kantra-cli-tests/data/applications/jee-example-app-1.0.0.ear --output /home/igor/MTA/reports-automation --source java-ee --rules /home/igor/github.com/kantra-cli-tests/data/xml/test.windup.xml
      

      2. Open resulting static report - it will not contain issue relative to the custom rule
      3. Open analysis log: it will contain line similar to this:

      time="2025-03-09T19:13:15+02:00" level=error msg="unable to load rule set" error="stat /home/igor/github.com/kantra-cli-tests/data/xml/ruleset.yaml: no such file or directory" logger=parser
      

      Actual results:

      Custom rule doesn't trigger any kind of issue, looks like name of custom rule is hardcoded somewhere

      Expected results:

      Custom rule should be applied properly 

      Additional info:
      See log and rule attached

        1. custom_rule_report.tar
          11.29 MB
          Igor Braginsky
        2. test.windup.xml
          1 kB
          Igor Braginsky

              emcmulla@redhat.com Emily McMullan
              ibragins@redhat.com Igor Braginsky
              Igor Braginsky Igor Braginsky
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: