Re: #elalto #appc APPC 404 in vFW "closed loop" #appc #elalto

Zhuangyang Chen

I managed to mount Netconf point.


But failed  to get the current streams being active in our Packet Generator, result is below


{"errors":{"error":[{"error-type":"protocol","error-tag":"data-missing","error-message":"Mount point does not exist."}]}}


I am not sure about the cause of “yang-ext:mount/sample-plugin:sample-plugin/pg-streams”  not exist. Apparently It is not an ODL feature, and wiki has very limited info.





From: <onap-discuss@...> on behalf of Brian Freeman <bf1936@...>
Reply to: <onap-discuss@...>, <bf1936@...>
Date: Friday, May 15, 2020 at 12:26 AM
To: "onap-discuss@..." <onap-discuss@...>, "CHO, TAKAMUNE" <tc012c@...>,
陈庄洋 <chenzhuangyang@...>
Subject: Re: [onap-discuss] #elalto #appc APPC 404 in vFW "closed loop"


Use the appc wiki page to check both config and operational data on the mount.


The mount state is probably in connecting still if there is a problem with the netconf hello message exchange.


Could be the vPacket Generator needs some adjustment 😊.






From: onap-discuss@... <onap-discuss@...> On Behalf Of CHO, TAKAMUNE
Sent: Thursday, May 14, 2020 12:22 PM
To: 陈庄洋 <chenzhuangyang@...>; onap-discuss@...
Subject: Re: [onap-discuss] #elalto #appc APPC 404 in vFW "closed loop"


***Security Advisory: This Message Originated Outside of AT&T ***
Reference for more information.

If that curl command gets result back, even it’s an error – that means restconf call from APPC is working.


It sounds like netconf mount has issue from the curl result




From: 陈庄洋 <chenzhuangyang@...>
Sent: Thursday, May 14, 2020 11:43 AM
To: onap-discuss@...; CHO, TAKAMUNE <tc012c@...>
Subject: Re: [onap-discuss] #elalto #appc APPC 404 in vFW "closed loop"


Hi Taka,


Unfortunately CMRI lab env is not able to make containers access the internet.


I try to curl from k8s node to appc svc IP, the result is listed below email.


From my perspective, the result would be the same with run curl inside the appc container. Would it be different?


The last thing I would try would be upload a APK package into appc container.






From: <onap-discuss@...> on behalf of Zhuangyang Chen <chenzhuangyang@...>
Reply to: <onap-discuss@...>, <chenzhuangyang@...>
Date: Wednesday, May 13, 2020 at 9:21 PM
To: <onap-discuss@...>, <tc012c@...>
Subject: Re: [onap-discuss] #elalto #appc APPC 404 in vFW "closed loop"


Hi Taka,


Considering appc container does not have curl, I try this curl command on k8s node by replacing localhost to appc IP.


The result indicates mount point does not exist?


root@k8s-node2:~# curl http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@...:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/9d8893f4-f158-451a-9828-46dfc610de71/yang-ext:mount/stream-count:stream-count/streams/


{"errors":{"error":[{"error-type":"protocol","error-tag":"data-missing","error-message":"Mount point does not exist."}]}}


However, I try to GET data by ODL APIDocs “GET /restconf/config/network-topology:network-topology/topology/{topology-id}/node/{node-id}”, result is data missing.



  "errors": {

    "error": [


        "error-type": "application",

        "error-tag": "data-missing",

        "error-message": "Request could not be completed because the relevant data model content does not exist "










From: <onap-discuss@...> on behalf of Taka Cho <tc012c@...>
Reply to: <onap-discuss@...>, <tc012c@...>
Date: Wednesday, May 13, 2020 at 8:59 PM
To: "onap-discuss@..." <onap-discuss@...>, "chenzhuangyang@..." <chenzhuangyang@...>
Subject: Re: [onap-discuss] #elalto #appc APPC 404 in vFW "closed loop"




There is appc.provider.vfodl.url in /opt/onap/appc/data/properties/ APPC docker


Try  curl http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/NODE_NAME/yang-ext:mount/stream-count:stream-count/streams/ to see if it worked from inside appc container.


The topologySevice code is here:;a=blob;f=appc-provider/appc-provider-bundle/src/main/java/org/onap/appc/provider/topology/;h=1a95d24ab54fda3a9adaeee5c6cf6e6e6a9e1e60;hb=bb3b3a39f5d5c68f3ae4ad1e7f6bf3f095fe9701



From: onap-discuss@... <onap-discuss@...> On Behalf Of zychen
Sent: Wednesday, May 13, 2020 4:47 AM
To: onap-discuss@...
Subject: [onap-discuss] #elalto #appc APPC 404 in vFW "closed loop"


Hi there,

In K8S Elato env, during on-boarding vFW. APPC encountered an 404 error:

APPC0060E Application null graph APPC:topology-operation-all:2.0.0 completed with failure: error code = 404, message = Not Found

In previous steps, APPC got Got 1 messages from DMaaP, Read 1 messages from APPC-CL as appcDemoEventListener/960. 

And Enrolled into TopologyService - modifyConfig() method.

However, I noticed the org.onap.appc.configURL is made to config DB in ODL, Should I consider to preload some data like SDNC in vFW? 

2020-05-13T01:07:00,459 | DEBUG | qtp1290089202-32909 | eelf                             | 444 - appc-common-bundle - 1.6.4 | Parameters passed to SLI: [ org.onap.appc.configURL = http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@appc:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/9d8893f4-f158-451a-9828-46dfc610de71/yang-ext:mount/stream-count:stream-count/streams/, org.onap.appc.reqid = c5bc35d5-fbf5-4619-a745-41665f01e21d, org.onap.appc.action = modifyConfig, org.onap.appc.configJson = {"streams": {"active-streams": 5}} ]



Join to automatically receive all group messages.