Uploaded image for project: 'Application Controller'
  1. Application Controller
  2. APPC-1367

APPC fails healthcheck with 404 error in some deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: High High
    • Dublin Release
    • Dublin Release, Casablanca Maintenance Release
    • None

      After ONAP is deployed in Integration lab (Integration-OOM-Daily tenant), APPC fails Robot healthcheck with 404. 

      ------------------------------------------------------------------------------
      Basic APPC Health Check | FAIL |
      404 != 200
      ------------------------------------------------------------------------------

      The detailed Robot log shows healthcheck request URL and response: 
       

      22:42:55.267 DEBUG http://appc.onap:8282 "POST /restconf/operations/SLI-API:healthcheck HTTP/1.1" 404 276           
      22:42:55.268 DEBUG post response: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/> <title>Error 404 </title> </head> <body> <h2>HTTP ERROR: 404</h2> <p>Problem accessing /restconf/operations/SLI-API:healthcheck. Reason: <pre> Not Found</pre></p> <hr /> </body> </html>

       

      container console log indicates karaf has started. the full console log is in attachment.  

       

      Apache Karaf starting up. Press Enter to open the shell now...
       92% [==================================================================> ]Starting the bundle
      100% [========================================================================]
      Karaf started in 280s. Bundle stats: 520 active, 521 total
      

       

      The issue only happens in some deployment under the same env.  

       

      Normally, the issue will go away if redeploying APPC module

       

       

       

        1. appc.console.log
          4.47 MB
        2. karaf.log
          4.62 MB

            xuyang11 xuyang11
            xuyang11 xuyang11
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: