Uploaded image for project: 'Network Controller'
  1. Network Controller
  2. SDNC-525

SDNC 3-node cluster only retrieves preload data a third of the time

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Highest Highest
    • Casablanca Release
    • Casablanca Release
    • sdnc-core
    • Today's SB04 environment.

      SB04 currently has a release deployment running, with SDNC in a 3-node cluster.

      integration-override is as follows:

      sdnc:
        replicaCount: 3
        config:
          enableClustering: true
      

      ete instantiate fails: http://10.12.6.24:30209/logs/0005_ete_instantiate/log.html

      Under the Instantiate Virtual Volume Group test, it fails because the SDNC preload validation fails with a 404.

      Manually calling the REST API from within the Robot pod:

      curl -v -u admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U -H 'Accept: application/json' -H 'Contentson' -H 'X-TransactionId: robot-ete-f7a76394-7c1a-4c38-9147-9d30daa74c65' -H 'X-FromAppId: robot-ete' http://sdnc.onap:8282/restconf/config/VNF-API:preload-vnfs/vnf-preload-list/Vfmodule_Ete_vVG_65bc4fa4-8656-4707-8a2b-1d51314cd47d/A1090774E49f42f8A26a..base_vvg..module-0
      

      Returns 404 about two-thirds of the time.

      The behavior seems to suggest  that the API only successfully returns the expected value if the API happens to land on the "right" SDNC node, and would return 404 if the other two nodes handle the request.

            gwu gwu
            gwu gwu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: