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

[CLI][DOC] Analysis fails sometimes when MTA CLI is upgraded without cleanup

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • MTA 8.0.0
    • MTA 8.0.0, MTA 7.3.1
    • Documentation
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      Description of problem:

      Analysis fails sometimes after several runs performed one by one

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

      How reproducible: sometimes after upgrading to next CLI version 

      Steps to Reproduce:
      1. Deploy and run analysis using older version
      2. Deploy newer version
      3. Run analsys again

      Actual results:

      $ /Users/ec2-user/.kantra/darwin-mta-cli analyze --overwrite --input /Users/ec2-user/kantra-cli-tests/data/applications/book-server --output /Users/ec2-user/kantra-cli-tests/reports-bookserver-local --source java-ee --source springboot --target cloud-readiness --target linux --target quarkus --run-local=true         
      INFO[0000] 
       --run-local set. running analysis in containerless mode 
      INFO[0000] running source analysis                      
      INFO[0000] setting provider from provider config         provider=java
      INFO[0000] starting provider                             provider=java
      ERRO[0130] unable to init the providers                  error="invalid header line \"An error has occurred. See the log file\"" provider=java
      ERRO[0130] unable to start Java provider                 error="invalid header line \"An error has occurred. See the log file\""
      

      Expected results:

      Analysis should be successful  

      Additional info:
      Need to update troubleshooting section and to mention that if this issue happens user should try to clear `.metadata` subfolder in the folder from where analysis command is performed. Also maven cache can be cleared to make sure nothing will interfere during next run

              rhn-support-anarnold A Arnold
              ibragins@redhat.com Igor Braginsky
              Igor Braginsky Igor Braginsky
              Mariya Pershina Mariya Pershina
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: