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

Not possible to call ansible healthcheck from SO VnfConfigUpdate workflow

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Dublin Release
    • Dublin Release, Casablanca Maintenance Release
    • APPC

      Then the SO VnfConfigUpdate is called no configuration parameters are passed in the request to APPC. This results in a failure to call the Ansible server with the error

      org.onap.ccsdk.sli.core.sli.SvcLogicException: Error constructing request for execution of playbook due to missing mandatory parameters. Reason = Ansible: Mandatory AnsibleAdapter key PlaybookName not found in parameters provided by calling agent !
      at org.onap.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:135) ~[?:?]
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
      at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]

      I think the problem is that if there are no parameters in the payload in the configuration-parameters the I think the merge of the template doesn't get called. If you look at the DG GenerateTemplateConfig.

      The problem is that if the merge isn't called then the later DGs fail.

      I have set up the template with a name coded in so no merge is needed .
      {
      "PlaybookName": "afr@0.0.cfg",
      "EnvParameters":

      { "ConfigFileName": "ABCDEFG" }

      ,
      "NodeList":["vMME"],
      "Timeout": 3600
      }

        1. Change.JPG
          Change.JPG
          37 kB
        2. Original.JPG
          Original.JPG
          43 kB

            jarmstrong001 jarmstrong001
            afenner afenner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: