Error 1 may be a symptom that the APPC DB hasn’t been populated correctly when it was installed. Connect to the sdnctl DB (user sdnctl, pwd gamma) and see if the VNF_TO_DG_MAPPING table has entries. If not, something went wrong during the DB installation. You may try to fix it by inserting the VNF to DG mappings manually (see SQL code below), but there’s a chance that other tables haven’t been populated as well, so you may have more problems later on.
insert into VNF_DG_MAPPING (VNF_DG_MAPPING_ID, ACTION, API_VERSION, VNF_TYPE, VNF_VERSION, DG_NAME, DG_VERSION, DG_MODULE) values (1, 'Restart', '2.00', '', '', 'Generic_Restart', '3.0.0', 'APPC'), (2, 'Configure', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (3, 'ConfigModify', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (4, 'Rebuild', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (5, 'Restart', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (6, 'HealthCheck', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (7, 'StartApplication', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (8, 'StopApplication', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (9, 'Migrate', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (10, 'Snapshot', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (11, 'ConfigRestore', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (12, 'ConfigBackup', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (13, 'Evacuate', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (14, 'Stop', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (15, 'Start', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (16, 'ConfigScaleOut', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (17, 'DistributeTraffic', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'), (18, 'DistributeTrafficCheck', NULL, NULL, NULL, 'DGOrchestrator', '4.0.0', 'APPC'); Error 2 is not a real issue, that topic isn’t used in ONAP. Error 4 is innocuous as well, please disregard it. Error 3 I don’t know honestly, it seems a logging/permission issue. Not sure how bad it is, but I wouldn’t be surprised if it’s another symptom that something went wrong during APPC instantiation. Taka, Can you please add more on this? For what regards error 1, is it possible to re-run only the job that populates the DB, or should one rebuild APPC from scratch? Thanks, Marco From: D'Alessandro Alessandro Gerardo <[email protected]> Date: Wednesday, August 28, 2019 at 12:32 PM To: "PLATANIA, MARCO (MARCO)" <[email protected]>, "VENKATESH KUMAR, VIJAY" <[email protected]>, "[email protected]" <[email protected]> Cc: "MALAKOV, YURIY" <[email protected]>, Malinconico Aniello Paolo <[email protected]>, Ferrero Marco Angelo <[email protected]> Subject: RE: vDNS use case / issue with SO pub about APPC-READ Hi Marco, Error about “future timestamp” in the APPC log has been fixed synchronizing all k8s VMs. Thanks. ONAP was able to read data from APPC-LCM-READ topic. Unfortunately other errors appeared in the APPC logs. Error 1: Error message (in the attached file) appears when a message from the topic APPC-LCM-READ has been consumed. AAI query works fine but the type of the VNF is set to “vLoadBalancer_20190821/null". Could be the “/null” the cause? Subsequently, in the same attached log, the VNF HealthCheck operation fails. Error2: we get the error ":"No such topic exists.-[APPC-CL]". Could you provide us with some details about such topic? Which ONAP component writes the DMaaP topic APPC-CL ? What are the difference of use between APPC-LCM-READ and APPC-CL as both seem to be read by the APPC? 2019-08-28 09:47:37,750 | INFO | Appc-Listener-2 | EventHandlerImpl | 426 - appc-common-bundle - 1.5.2 | Read 0 messages from APPC-CL as appcDemoEventListener/644. 2019-08-28 09:47:37,750 | INFO | Appc-Listener-2 | EventHandlerImpl | 426 - appc-common-bundle - 1.5.2 | Getting up to 1000 incoming events 2019-08-28 09:47:37,751 | INFO | Appc-Listener-2 | HttpDmaapConsumerImpl | 426 - appc-common-bundle - 1.5.2 | GET http://message-router.onap:3904/events/APPC-CL/appcDemoEventListener/644?timeout=60000&limit=1000<https://urldefense.proofpoint.com/v2/url?u=http-3A__message-2Drouter.onap-3A3904_events_APPC-2DCL_appcDemoEventListener_644-3Ftimeout-3D60000-26limit-3D1000&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jCmL-l23gGuesancWzmtqvwLt9aKeyN7ekDYKq69H1E&s=BkxnaNUchvAMaIHGRVYSe8CShDYJJ_81GJde3u7ZUUw&e=> 2019-08-28 09:47:37,757 | ERROR | Appc-Listener-2 | HttpDmaapConsumerImpl | 426 - appc-common-bundle - 1.5.2 | Did not get 200 from DMaaP. Got 404 - {"mrstatus":3001,"helpURL":"http://onap.readthedocs.io","message":"No<https://urldefense.proofpoint.com/v2/url?u=http-3A__onap.readthedocs.io-2522-2C-2522message-2522-3A-2522No&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jCmL-l23gGuesancWzmtqvwLt9aKeyN7ekDYKq69H1E&s=rTMTXQl47xMX6mnM_AY38y3YMk3n7euynUEL92jg19c&e=> such topic exists.-[APPC-CL]","status":404} 2019-08-28 09:47:37,757 | INFO | Appc-Listener-2 | HttpDmaapConsumerImpl | 426 - appc-common-bundle - 1.5.2 | Sleeping for 60s after failed request Error3: It is categorized like INFO (not ERROR) but a stack trace appears. Could be something the affect the normal APPC operation? 2019-08-28 09:46:37,749 | INFO | Appc-Listener-2 | HttpDmaapConsumerImpl | 426 - appc-common-bundle - 1.5.2 | Sleeping for 60s after failed request 2019-08-28 09:46:53,498 | INFO | Appc-Listener-1 | HttpDmaapConsumerImpl | 426 - appc-common-bundle - 1.5.2 | Got 0 messages from DMaaP 2019-08-28 09:46:53,498 | INFO | Appc-Listener-1 | EventHandlerImpl | 426 - appc-common-bundle - 1.5.2 | Read 0 messages from APPC-LCM-READ as APPC-EVENT-LISTENER-TEST/74. 2019-08-28 09:46:53,499 | INFO | Appc-Listener-1 | EventHandlerImpl | 426 - appc-common-bundle - 1.5.2 | Getting up to 10 incoming events 2019-08-28 09:46:53,499 | INFO | Appc-Listener-1 | HttpDmaapConsumerImpl | 426 - appc-common-bundle - 1.5.2 | GET http://message-router.onap:3904/events/APPC-LCM-READ/APPC-EVENT-LISTENER-TEST/74?timeout=60000&limit=10<https://urldefense.proofpoint.com/v2/url?u=http-3A__message-2Drouter.onap-3A3904_events_APPC-2DLCM-2DREAD_APPC-2DEVENT-2DLISTENER-2DTEST_74-3Ftimeout-3D60000-26limit-3D10&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jCmL-l23gGuesancWzmtqvwLt9aKeyN7ekDYKq69H1E&s=Mw-QLfuLmcrxC8BVM5rz2HZtCkXN--UfVSB4G4USPTw&e=> 2019-08-28 09:47:34,971 | INFO | s4j.pax.logging) | fileinstall | 7 - org.apache.felix.fileinstall - 3.6.4 | Unable to save configuration java.io.FileNotFoundException: /opt/opendaylight/etc/org.ops4j.pax.logging.cfg (Read-only file system) at java.io.FileOutputStream.open0(Native Method) ~[?:?] at java.io.FileOutputStream.open(FileOutputStream.java:270) [?:?] at java.io.FileOutputStream.<init>(FileOutputStream.java:213) [?:?] at java.io.FileOutputStream.<init>(FileOutputStream.java:162) [?:?] at org.apache.felix.fileinstall.internal.ConfigInstaller.doConfigurationEvent(ConfigInstaller.java:186) [7:org.apache.felix.fileinstall:3.6.4] at org.apache.felix.fileinstall.internal.ConfigInstaller.configurationEvent(ConfigInstaller.java:129) [7:org.apache.felix.fileinstall:3.6.4] at org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2090) [6:org.apache.felix.configadmin:1.8.16] at org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2058) [6:org.apache.felix.configadmin:1.8.16] at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141) [6:org.apache.felix.configadmin:1.8.16] at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109) [6:org.apache.felix.configadmin:1.8.16] at java.lang.Thread.run(Thread.java:748) [?:?] Error 4: this error highlights the lack of file blueprints-processor-adaptor.properties. Once this error appears, APPC processing exits waiting for next request. Could be due to something that went wrong in the distribution or instantiation phase? Could it be a bug of APPC release we are using i.e. Image: nexus3.onap.org:10001/onap/appc-image:1.5.3 ? 2019-08-28 09:47:53,601 | INFO | Appc-Listener-1 | HttpDmaapConsumerImpl | 426 - appc-common-bundle - 1.5.2 | Got 0 messages from DMaaP 2019-08-28 09:47:53,602 | INFO | Appc-Listener-1 | EventHandlerImpl | 426 - appc-common-bundle - 1.5.2 | Read 0 messages from APPC-LCM-READ as APPC-EVENT-LISTENER-TEST/74. 2019-08-28 09:47:53,603 | INFO | Appc-Listener-1 | EventHandlerImpl | 426 - appc-common-bundle - 1.5.2 | Getting up to 10 incoming events 2019-08-28 09:47:53,604 | INFO | Appc-Listener-1 | HttpDmaapConsumerImpl | 426 - appc-common-bundle - 1.5.2 | GET http://message-router.onap:3904/events/APPC-LCM-READ/APPC-EVENT-LISTENER-TEST/74?timeout=60000&limit=10<https://urldefense.proofpoint.com/v2/url?u=http-3A__message-2Drouter.onap-3A3904_events_APPC-2DLCM-2DREAD_APPC-2DEVENT-2DLISTENER-2DTEST_74-3Ftimeout-3D60000-26limit-3D10&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jCmL-l23gGuesancWzmtqvwLt9aKeyN7ekDYKq69H1E&s=Mw-QLfuLmcrxC8BVM5rz2HZtCkXN--UfVSB4G4USPTw&e=> 2019-08-28 09:48:05,969 | ERROR | pool-30-thread-1 | ConfigRestAdaptorServiceImpl | 358 - wrap_file__opt_opendaylight_system_com_att_eelf_eelf-core_1.0.0_eelf-core-1.0.0.jar - 0.0.0 | Failed to load properties for file: {} blueprints-processor-adaptor.properties java.io.FileNotFoundException: /blueprints-processor-adaptor.properties (No such file or directory) at java.io.FileInputStream.open0(Native Method) ~[?:?] at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:?] at java.io.FileInputStream.<init>(FileInputStream.java:138) ~[?:?] at java.io.FileInputStream.<init>(FileInputStream.java:93) ~[?:?] at org.onap.ccsdk.features.rest.adaptor.service.ConfigRestAdaptorServiceImpl.doLoadFromPath(ConfigRestAdaptorServiceImpl.java:99) ~[?:?] at org.onap.ccsdk.features.rest.adaptor.service.ConfigRestAdaptorServiceImpl.loadProps(ConfigRestAdaptorServiceImpl.java:91) ~[?:?] at org.onap.ccsdk.features.rest.adaptor.service.ConfigRestAdaptorServiceImpl.lambda$new$0(ConfigRestAdaptorServiceImpl.java:60) ~[?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] Thank you for the help. Marco Ferrero Alessandro D’Alessandro. From: PLATANIA, MARCO (MARCO) [mailto:[email protected]] Sent: giovedì 22 agosto 2019 19:00 To: D'Alessandro Alessandro Gerardo <[email protected]>; VENKATESH KUMAR, VIJAY <[email protected]>; [email protected] Cc: MALAKOV, YURIY <[email protected]>; Malinconico Aniello Paolo <[email protected]>; Ferrero Marco Angelo <[email protected]> Subject: [EXT] Re: vDNS use case / issue with SO pub about APPC-READ Messages published in APPC-LCM-WRITE definitely come from APPC (unless you set the topics differently, which is not the common case). APPC reads from APP-LCM-READ (which is where clients like SO publish). Being APPC-LCM-WRITE a shared channel between APPC and possibly multiple clients, the originator ID is just to express which client sent the input message (in APP-LCM-READ). I believe this is why you see MSO as originator ID. Regarding the actual error, I think your K8S cluster has some nodes out of sync. Try to see if the timestamps in the VMs (or physical hosts) are synchronized. I’m quite sure that’s not an ONAP-related issue. Marco From: D'Alessandro Alessandro Gerardo <[email protected]<mailto:[email protected]>> Date: Thursday, August 22, 2019 at 11:42 AM To: "PLATANIA, MARCO (MARCO)" <[email protected]<mailto:[email protected]>>, "VENKATESH KUMAR, VIJAY" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: "MALAKOV, YURIY" <[email protected]<mailto:[email protected]>>, Malinconico Aniello Paolo <[email protected]<mailto:[email protected]>>, Ferrero Marco Angelo <[email protected]<mailto:[email protected]>> Subject: vDNS use case / issue with SO pub about APPC-READ Hi All, we are continue working on vDNS use case (https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_scaleout.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.onap.org_en_latest_submodules_integration.git_docs_docs-5Fscaleout.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=Ekz-JaW-tqb_9ez8Ega7r0qZxSQhjv3j1pm0o-h9Zxc&s=jAPoI0SHTOvhhanTDp8C9-qWxkJL362KPb0llxLW9lM&e=> ) primarily focusing on closed loop aspects we successfully carried out the following steps related to the above guide “PART 1 - Service Definition and Onboarding” “PART 2 - Scale Out Use Case Instantiation” “PART 3 - Post Instantiation Operations” “3-1 Using the VNF : vLB Manual Configuration”… skipped because it was carried out automatically “3-2 Updating AAI with VNF resources” After this steps we see vPKG does NOT generates packets. Anyway making that working is not our primary goal at this stage. We changed the TCA rules as “if packets are LESS than 2000 than call policy operation” and this rules is always satisfied in our case. In fact we have seen MSO publishing a topic “APPC-LCM-READ” asking for "action":"HealthCheck". Refer to attached file “APPC_LCM_READ_messagerouter” In the APP-C log you can also find “InvalidInputException : Input Timestamp is of future” associated to the messages related to the topic “APPC-LCM-READ”. Refer to attached file “appc_log_errortimestamp” Afterwards we have noticed under topic “APPC-LCM-WRITE” the following "message":"INVALID INPUT PARAMETER - Input Timestamp is of future = Thu Aug 22 10:28:58 GMT 2019" followed by the "message":"UNEXPECTED ERROR - java.lang.IllegalStateException". Refer to attached file “APPC_LCM_WRITE_messagerouter”. Such messages are apparently published by MSO because that is the name associated to the field "originator-id" while we expected it was published by APPC as we understood from the GET http://message-router.onap:3904/events/APPC-LCM-WRITE<https://urldefense.proofpoint.com/v2/url?u=http-3A__message-2Drouter.onap-3A3904_events_APPC-2DLCM-2DWRITE&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=Ekz-JaW-tqb_9ez8Ega7r0qZxSQhjv3j1pm0o-h9Zxc&s=lJuY76o6hiV1tuZyiiiaWx_-JzKI1pYoMZWHt9UtXYw&e=> found in “bpmn_debug_cut.log”). In the MSO log you can find the following error “Error Message: Unable to invoke action : HealthCheck”. Refer to attached file “bpmn_debug_cut.log” Do you have any suggestion how to fix such issue? Is there any document describing the semantic of messages published from both MSO and APPC? Thanks in advance Best regards, Alessandro [https://img.tim.it:443/sdr/banner-mail-dipe.jpg]<https://urldefense.proofpoint.com/v2/url?u=https-3A__on.tim.it_banner-2Dmail-2Ddip&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jCmL-l23gGuesancWzmtqvwLt9aKeyN7ekDYKq69H1E&s=TSYO9yoUgRuUT8bL3OfEAzwq3mrr-1_YEFLnrqra8Hs&e=> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non è necessario. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18739): https://lists.onap.org/g/onap-discuss/message/18739 Mute This Topic: https://lists.onap.org/mt/32991141/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
