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 ๐. Brian From: [email protected] <[email protected]> On Behalf Of CHO, TAKAMUNE Sent: Thursday, May 14, 2020 12:22 PM To: ้ๅบๆด <[email protected]>; [email protected] Subject: Re: [onap-discuss] #elalto #appc APPC 404 in vFW "closed loop" ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html 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 Taka From: ้ๅบๆด <[email protected]<mailto:[email protected]>> Sent: Thursday, May 14, 2020 11:43 AM To: [email protected]<mailto:[email protected]>; CHO, TAKAMUNE <[email protected]<mailto:[email protected]>> 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. Regards, Zhuangyang From: <[email protected]<mailto:[email protected]>> on behalf of Zhuangyang Chen <[email protected]<mailto:[email protected]>> Reply to: <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>> Date: Wednesday, May 13, 2020 at 9:21 PM To: <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>> 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:[email protected]:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/9d8893f4-f158-451a-9828-46dfc610de71/yang-ext:mount/stream-count:stream-count/streams/<https://urldefense.proofpoint.com/v2/url?u=http-3A__admin-3AKp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U-4010.108.131.179-3A8282_restconf_config_network-2Dtopology-3Anetwork-2Dtopology_topology_topology-2Dnetconf_node_9d8893f4-2Df158-2D451a-2D9828-2D46dfc610de71_yang-2Dext-3Amount_stream-2Dcount-3Astream-2Dcount_streams_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=MmauRnGaC8z8v8yrWaS9izrrIxDX4jOSd6NJXoXTyek&s=B7Y7hMfdp8CRH3T6l-HeLSlEYpi-6IPngSPOBmlKgls&e=> {"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 " } ] } } Regards, Zhuangyang From: <[email protected]<mailto:[email protected]>> on behalf of Taka Cho <[email protected]<mailto:[email protected]>> Reply to: <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>> Date: Wednesday, May 13, 2020 at 8:59 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] #elalto #appc APPC 404 in vFW "closed loop" HI, There is appc.provider.vfodl.url in /opt/onap/appc/data/properties/appc.property 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: https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-provider/appc-provider-bundle/src/main/java/org/onap/appc/provider/topology/TopologyService.java;h=1a95d24ab54fda3a9adaeee5c6cf6e6e6a9e1e60;hb=bb3b3a39f5d5c68f3ae4ad1e7f6bf3f095fe9701<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dblob-3Bf-3Dappc-2Dprovider_appc-2Dprovider-2Dbundle_src_main_java_org_onap_appc_provider_topology_TopologyService.java-3Bh-3D1a95d24ab54fda3a9adaeee5c6cf6e6e6a9e1e60-3Bhb-3Dbb3b3a39f5d5c68f3ae4ad1e7f6bf3f095fe9701&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=MmauRnGaC8z8v8yrWaS9izrrIxDX4jOSd6NJXoXTyek&s=fLbocQdkpSR9eGXPcWq7ydN-l9EtsPPZgrE-FzzGgmA&e=> Taka From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of zychen Sent: Wednesday, May 13, 2020 4:47 AM To: [email protected]<mailto:[email protected]> 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/<https://urldefense.proofpoint.com/v2/url?u=http-3A__admin-3AKp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U-40appc-3A8282_restconf_config_network-2Dtopology-3Anetwork-2Dtopology_topology_topology-2Dnetconf_node_9d8893f4-2Df158-2D451a-2D9828-2D46dfc610de71_yang-2Dext-3Amount_stream-2Dcount-3Astream-2Dcount_streams_&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=0ngRnhAg9QFC1M3lJA5gaT6F0E_OiNXAbKCXpjrbPmI&s=M6OeuLAgGD1Ay_pSVqwfKEonsKgCmXufsijW3DC_OBA&e=>, org.onap.appc.reqid = c5bc35d5-fbf5-4619-a745-41665f01e21d, org.onap.appc.action = modifyConfig, org.onap.appc.configJson = {"streams": {"active-streams": 5}} ] Regards, Irving -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21090): https://lists.onap.org/g/onap-discuss/message/21090 Mute This Topic: https://lists.onap.org/mt/74177301/21656 Mute #appc: https://lists.onap.org/mk?hashtag=appc&subid=2740164 Mute #elalto: https://lists.onap.org/mk?hashtag=elalto&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
