Re: vDNS use case / issue with SO pub about APPC-READ


Taka Cho
 

VNF_DG_MAPPING table should not be empty after deploying APPC helm chart.

 

Here is the pre-load values for APPC DB

https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/resources/sqlData.dump;h=9d28eb53e78be42b9bef0f9e7ef01e195e215ef1;hb=9035495b03de1814d811f3a0c23959f55853616d

 

I think something is wrong when deploying APPC helm .. make sure you cleanup pv, pvc and remove the content for APPC on NFS share mount point.

 

Taka

 

From: Ferrero Marco Angelo <marco.ferrero@...>
Sent: Thursday, August 29, 2019 11:14 AM
To: onap-discuss@...; PLATANIA, MARCO <platania@...>; D'Alessandro Alessandro Gerardo <alessandro.dalessandro@...>; VENKATESH KUMAR, VIJAY <vv770d@...>
Cc: MALAKOV, YURIY <ym9479@...>; Malinconico Aniello Paolo <a.malinconico@...>; CHO, TAKAMUNE <tc012c@...>
Subject: R: vDNS use case / issue with SO pub about APPC-READ

 

Hi Marco,

We have sdnctl database both in

dev-mariadb-galera-mariadb-galera database (seem to be the master database of ONAP)

and

dev-appc-appc-db (APPC specific database).

 

In both cases all the tables whose name begin with VNF are empty.

Which of the two should I consider ?

 

Following I report the analisys of the appc database.

 

root@cp-1:~/oom/kubernetes# kubectl exec -n onap -ti dev-appc-appc-db-0 -- bash

bash-4.2$ mysql -usdnctl -pgamma

Welcome to the MariaDB monitor.  Commands end with ; or \g.

Your MariaDB connection id is 363170

Server version: 10.1.24-MariaDB MariaDB Server

 

Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others.

 

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

 

MariaDB [(none)]> use sdnctl;

Reading table information for completion of table and column names

You can turn off this feature to get a quicker startup with -A

 

Database changed

MariaDB [sdnctl]> show tables like 'VNF%';

+-----------------------------+

| Tables_in_sdnctl (VNF%)     |

+-----------------------------+

| VNF                         |

| VNFC_DG_MAPPING             |

| VNFC_REFERENCE              |

| VNF_DG_MAPPING              |

| VNF_IMAGE                   |

| VNF_LOCK_MANAGEMENT         |

| VNF_MODEL_LICENSES          |

| VNF_MODEL_LICENSE_FEATURES  |

| VNF_NETWORKS                |

| VNF_NETWORK_CONNECTION      |

| VNF_NETWORK_CONNECTION_VLAN |

| VNF_PROFILE                 |

| VNF_STATE_MANAGEMENT        |

+-----------------------------+

13 rows in set (0.00 sec)

 

MariaDB [sdnctl]> describe VNF_DG_MAPPING;

+-------------------+--------------+------+-----+---------+----------------+

| Field             | Type         | Null | Key | Default | Extra          |

+-------------------+--------------+------+-----+---------+----------------+

| VNF_DG_MAPPING_ID | int(11)      | NO   | PRI | NULL    | auto_increment |

| ACTION            | varchar(50)  | NO   |     | NULL    |                |

| API_VERSION       | varchar(50)  | YES  |     | NULL    |                |

| VNF_TYPE          | varchar(150) | YES  |     | NULL    |                |

| VNF_VERSION       | varchar(50)  | YES  |     | NULL    |                |

| DG_NAME           | varchar(50)  | NO   |     | NULL    |                |

| DG_VERSION        | varchar(50)  | YES  |     | NULL    |                |

| DG_MODULE         | varchar(50)  | NO   |     | NULL    |                |

+-------------------+--------------+------+-----+---------+----------------+

8 rows in set (0.00 sec)

 

MariaDB [sdnctl]> select * from VNF_DG_MAPPING;

Empty set (0.00 sec)

 

Table empty as you wrote in your response Marco Platania.

 

Looking at the appc-db helm config:

 

  appc-db:

    Container ID:   docker://1c7944555847290b74553ed53245cf28ff457c5d45585b192369b8cc59255d1c

    Image:          nexus3.onap.org:10001/adfinissygroup/k8s-mariadb-galera-centos:v002

    Image ID:       docker-pullable://nexus3.onap.org:10001/adfinissygroup/k8s-mariadb-galera-centos@sha256:fbcb842f30065ae94532cb1af9bb03cc6e2acaaf896d87d0ec38da7dd09a3dde

    Ports:          3306/TCP, 4444/TCP, 4567/TCP, 4568/TCP

    Host Ports:     0/TCP, 0/TCP, 0/TCP, 0/TCP

    State:          Running

      Started:      Thu, 08 Aug 2019 14:24:37 +0000

    Ready:          True

    Restart Count:  0

    Liveness:       exec [mysqladmin ping] delay=60s timeout=5s period=10s #success=1 #failure=3

    Readiness:      exec [/usr/share/container-scripts/mysql/readiness-probe.sh] delay=30s timeout=5s period=10s #success=1 #failure=3

    Environment:

      POD_NAMESPACE:        onap (v1:metadata.namespace)

      MYSQL_USER:           my-user

      MYSQL_PASSWORD:       <set to the key 'user-password' in secret 'dev-appc-appc-db'>  Optional: false

      MYSQL_DATABASE:       my-database

      MYSQL_ROOT_PASSWORD:  <set to the key 'db-root-password' in secret 'dev-appc-appc-db'>  Optional: false

    Mounts:

      /etc/localtime from localtime (ro)

      /var/lib/mysql from dev-appc-appc-db-data (rw)

      /var/run/secrets/kubernetes.io/serviceaccount from default-token-wvnv6 (ro)

Conditions:

  Type              Status

  Initialized       True

  Ready             True

  ContainersReady   True

  PodScheduled      True

 

It mounts db in the directory /var/lib/mysql from the persistent volume named dev-appc-appc-db-data.

Persistent volumes are correctly set as you can see from the following command.

 

root@cp-1:~/oom/kubernetes# kubectl get pv -n onap | grep 'NAME\|dev-appc-appc-db-data'

NAME                                           CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM                                                                               STORAGECLASS                               REASON   AGE

dev-appc-appc-db-data0                         2Gi        RWX            Retain           Bound       onap/dev-appc-appc-db-data-dev-appc-appc-db-1                                       dev-appc-appc-db-data                               21d

dev-appc-appc-db-data1                         2Gi        RWX            Retain           Bound       onap/dev-appc-appc-db-data-dev-appc-appc-db-0                                       dev-appc-appc-db-data                               21d

dev-appc-appc-db-data2                         2Gi        RWX            Retain           Bound       onap/dev-appc-appc-db-data-dev-appc-appc-db-2                                       dev-appc-appc-db-data                               21d

 

Unfortunately I was not able to locate the job that populates this databases. It does not appear in these ones:

 

root@cp-1:~/oom/kubernetes# kubectl get jobs -n onap

NAME                                       COMPLETIONS   DURATION   AGE

dev-aaf-aaf-sms-preload                    1/1           4m16s      21d

dev-aaf-aaf-sshsm-distcenter               1/1           12s        21d

dev-aaf-aaf-sshsm-testca                   1/1           25s        21d

dev-aai-aai-graphadmin-create-db-schema    1/1           14m        21d

dev-aai-aai-traversal-update-query-data    1/1           22m        21d

dev-contrib-netbox-app-provisioning        1/1           4m46s      21d

dev-oof-music-cassandra-job-config         1/1           12m        21d

dev-oof-oof-has-healthcheck                1/1           24m        21d

dev-oof-oof-has-onboard                    1/1           23m        21d

dev-pnda-dcae-pnda-bootstrap               1/1           4m19s      21d

dev-portal-portal-db-config                1/1           11m        21d

dev-sdc-sdc-be-config-backend              1/1           20m        20d

dev-sdc-sdc-cs-config-cassandra            1/1           81s        20d

dev-sdc-sdc-dcae-be-tools                  1/1           27m        20d

dev-sdc-sdc-es-config-elasticsearch        1/1           4m38s      20d

dev-sdc-sdc-onboarding-be-cassandra-init   1/1           3m22s      20d

dev-sdc-sdc-wfd-be-workflow-init           1/1           3m42s      20d

dev-so-so-mariadb-config-job               1/1           4m50s      21d

dev-vid-vid-galera-config                  1/1           7m28s      21d

dev-vnfsdk-vnfsdk-init-postgres            1/1           15m        21d

 

root@cp-1:~/oom/kubernetes# kubectl get jobs -n onap | grep appc

 

All jobs are completed so it’s all ok.

As you can see no one refers to appc even if there are some jobs that initialize aai, portal, so, vid and vnfsdk databases.

We would greatly appreciate if you can indicate us the job that populates the appc db.

 

Thank you a lot.

 

Marco Ferrero

Alessandro D’Alessadro

------------------------------------------------------------------
TIM

Marco Angelo Ferrero
Mobile & Fixed Innovation
IP, Transport & Core Innovation

TIM S.p.A.
Via G. Reiss Romoli, 274 – 10148 TORINO
+39 011 2286739
+39 331 6001354

 

Da: onap-discuss@... [mailto:onap-discuss@...] Per conto di Marco Platania
Inviato: mercoledì 28 agosto 2019 19:56
A: D'Alessandro Alessandro Gerardo; VENKATESH KUMAR, VIJAY; onap-discuss@...
Cc: MALAKOV, YURIY; Malinconico Aniello Paolo; Ferrero Marco Angelo; CHO, TAKAMUNE
Oggetto: [EXT] Re: [onap-discuss] vDNS use case / issue with SO pub about APPC-READ

 

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 <alessandro.dalessandro@...>
Date: Wednesday, August 28, 2019 at 12:32 PM
To: "PLATANIA, MARCO (MARCO)" <platania@...>, "VENKATESH KUMAR, VIJAY" <vv770d@...>, "onap-discuss@..." <onap-discuss@...>
Cc: "MALAKOV, YURIY" <ym9479@...>, Malinconico Aniello Paolo <a.malinconico@...>, Ferrero Marco Angelo <marco.ferrero@...>
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

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 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

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

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:platania@...]
Sent: giovedì 22 agosto 2019 19:00
To: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@...>; VENKATESH KUMAR, VIJAY <vv770d@...>; onap-discuss@...
Cc: MALAKOV, YURIY <ym9479@...>; Malinconico Aniello Paolo <a.malinconico@...>; Ferrero Marco Angelo <marco.ferrero@...>
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 <alessandro.dalessandro@...>
Date: Thursday, August 22, 2019 at 11:42 AM
To: "PLATANIA, MARCO (MARCO)" <platania@...>, "VENKATESH KUMAR, VIJAY" <vv770d@...>, "onap-discuss@..." <onap-discuss@...>
Cc: "MALAKOV, YURIY" <ym9479@...>, Malinconico Aniello Paolo <a.malinconico@...>, Ferrero Marco Angelo <marco.ferrero@...>
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 ) 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 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

 

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.

 

Join onap-discuss@lists.onap.org to automatically receive all group messages.