Date   
Re: #ccsdk Committer promotion : Brinda Santh Muthuramalingam #ccsdk

Brinda S Muthuramalingam
 

Thanks Brian !


Regards
Brinda Santh M | brindasanth@... | bsminus@... | bs2796@... | +1 732 781 5923




From:        "Brian" <bf1936@...>
To:        "onap-discuss@..." <onap-discuss@...>, "TIMONEY, DAN" <dt5972@...>
Date:        07/16/2019 08:59 AM
Subject:        [EXTERNAL] Re: [onap-discuss] #ccsdk Committer promotion : Brinda Santh Muthuramalingam
Sent by:        onap-discuss@...



Congrats Brinda !

 

Brian

 

 

From:onap-discuss@... <onap-discuss@...> On Behalf Of TIMONEY, DAN
Sent:
Tuesday, July 16, 2019 8:49 AM
To:
onap-discuss <onap-discuss@...>
Subject:
[onap-discuss] #ccsdk Committer promotion : Brinda Santh Muthuramalingam

 

***Security Advisory:This Message Originated Outside of AT&T ***
Reference
http://cso.att.com/EmailSecurity/IDSP.htmlfor more information.

It gives me great pleasure to announce that Brinda Santh Muthuramalingam has been promoted to committer status for the CCSDK project.

 

Thanks, Brinda, for your many contributions to the CCSDK project to date, and congratulations on this well deserved promotion!

 

Dan

 

Dan Timoney

Principal Technical Staff Member

AT&T

Email : dtimoney@...

Office : +1 (732) 420-3226

Mobile : +1 (201) 960-1211

200 S Laurel Ave, Rm E2-2A03

Middletown, NJ 08873





Re: #ccsdk Committer promotion : Brinda Santh Muthuramalingam #ccsdk

Brinda S Muthuramalingam
 

Thanks Dan !


Regards
Brinda Santh M | brindasanth@... | bsminus@... | bs2796@... | +1 732 781 5923




From:        "TIMONEY, DAN" <dtimoney@...>
To:        " onap-discuss" <onap-discuss@...>
Date:        07/16/2019 08:49 AM
Subject:        [EXTERNAL] [onap-discuss] #ccsdk Committer promotion : Brinda Santh Muthuramalingam
Sent by:        onap-discuss@...



It gives me great pleasure to announce that Brinda Santh Muthuramalingam has been promoted to committer status for the CCSDK project.

 

Thanks, Brinda, for your many contributions to the CCSDK project to date, and congratulations on this well deserved promotion!

 

Dan

 

Dan Timoney

Principal Technical Staff Member

AT&T

Email : dtimoney@...

Office : +1 (732) 420-3226

Mobile : +1 (201) 960-1211

200 S Laurel Ave, Rm E2-2A03

Middletown, NJ 08873





Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Marco Platania
 

Rajendra,

Please run heat bridge after you install the VNF, it seems that VNF-C aspects aren’t found because not set in AAI.

Marco


On Jul 22, 2019, at 12:50 PM, Rajendra Prasad Mishra <rpmishra@...> wrote:

Hi Taka, Steve,
   I am facing exactly the same problem as mentioned by Steve on Casablanca release. While doing "stop" LCM operation I get the 450 error.
As I understood from the the email chain, the problem was due to "capability-test" not passing. 

I see in the email thread that the error was somehow resolved. Can you please share the recipe for the fix.
I do not have a VNFC, hope that is not causing the problem. My vnf is the simple vLB (load balancer with DNS).

Here is the snippet of the log .
---------------------------------
2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | CONFIGTYPE=
2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vm-count=3
2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | skip-hypervisor-check=true
2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | request-action=Stop
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | input.action=Stop
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vnf.ipv4-oam-address=10.10.10.100
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | configuration-params=
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | VNFCNAME0=
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | template-name=
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vm[1].tenant-id=5a7c7f86fcaa418f83be664f921bf4ee
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | getVnfcFunctionCodeForVserver()::vnfcFunctionCode=null
20ppc-config-data-services - 1.4.4 | processCapabilitiesForVMLevel() :: vnfcFunctionCode is not present in context!!!
      | 509 - appc-config-data-services - 1.4.4 | getCapability Successful
19-07-22T12:26:38,996 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | processCapabilitiesForVMLevel() :: vnfcFunctionCode is not present in context!!!
2019-07-22T12:26:38,996 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | getCapability Successful
.
.
.
2019-07-22T12:26:39,000 | INFO  | appc-dispatcher-4 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 47 (execute)
2019-07-22T12:26:39,011 | INFO  | appc-dispatcher-4 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome (success) not found, keys are { (failure)}
2019-07-22T12:26:39,011 | INFO  | appc-dispatcher-4 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome (Other) not found, keys are { (failure)}
2019-07-22T12:26:39,036 | INFO  | appc-dispatcher-4 | audit                            | 458 - appc-common-bundle - 1.4.4 | APPC0090A Operation "Stop" for VNF type "097d2826-1949-4ad8-ab4f-dc2e27e94022" from Source "SDNGP" with RequestID "386d0f72-5495-4a50-b7fc-7e4003d8335c" was started at "2019-07-22T12:26:37Z" and ended at "2019-07-22T12:26:39Z" with status code "450"
---------------------------------

thanks,
-RP

Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Taka Cho
 

Your response return code is: 450

 

Based on https://docs.onap.org/en/dublin/submodules/appc.git/docs/APPC%20LCM%20API%20Guide/APPC%20LCM%20API%20Guide.html,

 

450

REQUEST NOT SUPPORTED

 

It sounds like your request format has issue.

 

Taka

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rajendra Prasad Mishra
Sent: Monday, July 22, 2019 12:50 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Subject: Re: [onap-discuss] APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Hi Taka, Steve,
   I am facing exactly the same problem as mentioned by Steve on Casablanca release. While doing "stop" LCM operation I get the 450 error.
As I understood from the the email chain, the problem was due to "capability-test" not passing. 

I see in the email thread that the error was somehow resolved. Can you please share the recipe for the fix.
I do not have a VNFC, hope that is not causing the problem. My vnf is the simple vLB (load balancer with DNS).

Here is the snippet of the log .
---------------------------------

2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | CONFIGTYPE=

2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vm-count=3

2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | skip-hypervisor-check=true

2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | request-action=Stop

2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | input.action=Stop

2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vnf.ipv4-oam-address=10.10.10.100

2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | configuration-params=

2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | VNFCNAME0=

2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | template-name=

2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vm[1].tenant-id=5a7c7f86fcaa418f83be664f921bf4ee

2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | getVnfcFunctionCodeForVserver()::vnfcFunctionCode=null

20ppc-config-data-services - 1.4.4 | processCapabilitiesForVMLevel() :: vnfcFunctionCode is not present in context!!!

      | 509 - appc-config-data-services - 1.4.4 | getCapability Successful

19-07-22T12:26:38,996 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | processCapabilitiesForVMLevel() :: vnfcFunctionCode is not present in context!!!

2019-07-22T12:26:38,996 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | getCapability Successful

.

.
.

2019-07-22T12:26:39,000 | INFO  | appc-dispatcher-4 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 47 (execute)

2019-07-22T12:26:39,011 | INFO  | appc-dispatcher-4 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome (success) not found, keys are { (failure)}

2019-07-22T12:26:39,011 | INFO  | appc-dispatcher-4 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome (Other) not found, keys are { (failure)}

2019-07-22T12:26:39,036 | INFO  | appc-dispatcher-4 | audit                            | 458 - appc-common-bundle - 1.4.4 | APPC0090A Operation "Stop" for VNF type "097d2826-1949-4ad8-ab4f-dc2e27e94022" from Source "SDNGP" with RequestID "386d0f72-5495-4a50-b7fc-7e4003d8335c" was started at "2019-07-22T12:26:37Z" and ended at "2019-07-22T12:26:39Z" with status code "450"

---------------------------------


thanks,
-RP

Re: K8s in ONAP - DDF follow up

Srini
 

Hi Ritu,

Can you check? Could this be due to not using default namespace in helm charts?

Srini

 

From: Konrad Banka [mailto:k.banka@...]
Sent: Monday, July 22, 2019 7:18 AM
To: Łukasz Rajewski <lukasz.rajewski@...>; Konrad Banka <k.banka@...>
Cc: Rajewski Łukasz - Korpo <Lukasz.Rajewski@...>; onap-discuss@...; Kamineni, Kiran K <kiran.k.kamineni@...>; Addepalli, Srinivasa R <srinivasa.r.addepalli@...>; Zhu, Libo <libo.zhu@...>; Sood, Ritu <ritu.sood@...>; Jayathirth, Pramod Raghavendra <pramod.raghavendra.jayathirth@...>; Multanen, Eric W <eric.w.multanen@...>
Subject: RE: Re: Re: K8s in ONAP - DDF follow up

 

Hi again,

I've managed to launch some more basic tests today and it looks like my change doesn't fix this issue completely. It fixes creating network resources and they are created correctly (please see log below), however pods are having issues with creating sandbox due to multus issues. Nevertheless I think that pod sandbox issue may have root cause anchored somewhere else, so probably additional fix may be needed.

``` k8plugin logs:
2019/07/22 14:14:42 Generate MAC address
2019/07/22 14:14:42 ovn4nfvk8s_protected-private-net created
2019/07/22 14:14:42 Processing Kind: Network
2019/07/22 14:14:42 Processing file: /tmp/helm-tmpl-522893518/firewall/templates/unprotected-private-net.yaml-0
2019/07/22 14:14:42 Reading YAML file
2019/07/22 14:14:42 Decoding deployment YAML
2019/07/22 14:14:42 Generate MAC address
2019/07/22 14:14:42 ovn4nfvk8s_unprotected-private-net created
::1 - - [22/Jul/2019:14:14:41 +0000] "POST /v1/instance HTTP/1.1" 201 844 

```
``` ovn ports status (previously logical switches were not created)
vagrant@multicloud"~/multicloud-k8s/kud/tests [0]$ ovn-nbctl  --db tcp:$OVN_CENTRAL_ADDRESS lrp-list ovn4nfv-master
d5845420-25d9-4906-86c7-772cfee7abef (rtoj-ovn4nfv-master)
ccfd83e0-6b9f-43fb-aa54-1b7c5b462220 (rtos-onap-private-net)
9ad14ed7-ab33-479f-a336-cb9702e57daf (rtos-protected-private-net)
bee4790a-af0b-4f4f-9270-018e04e2a606 (rtos-unprotected-private-net) 
```
``` pods status

vagrant@multicloud"~/multicloud-k8s/kud/tests [0]$ kubectl describe -n vfw-test pods test-sink-5 | tail -n 3
  Normal   SandboxChanged          3m28s (x12 over 4m46s)  kubelet, minion02  Pod sandbox changed, it will be killed and re-created.
  Warning  FailedCreatePodSandBox  3m21s (x4 over 3m43s)   kubelet, minion02  (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "525b3aae9d1c2fe4b778ec4efa65460aa5d867ac2593ead1d71c30fd87f715dd" network for pod "test-sink-5456988b6c-qq754": NetworkPlugin cni failed to set up pod "test-sink-5456988b6c-qq754_vfw-test" network: Multus: Err in loading K8s Delegates k8s args: Multus: Err in getting k8s network from pod: GetPodNetwork: failed getting the delegate: getKubernetesDelegate: failed to get network resource, refer Multus README.md for the usage guide: the server could not find the requested resource
```

 

--------- Original Message ---------

Sender : Łukasz Rajewski <lukasz.rajewski@...>

Date : 2019-07-22 16:00 (GMT+2)

Title : Re: Re: K8s in ONAP - DDF follow up

 

So I have reported it in here

 

https://jira.onap.org/browse/MULTICLOUD-731

 

Lukasz

 

 

On Mon, Jul 22, 2019 at 3:54 PM Konrad Banka <k.banka@...> wrote:

Hi Łukasz, All

I came across the same issue as you today. I think I've located culprit of this error and I've addressed it in review https://gerrit.onap.org/r/c/multicloud/k8s/+/91812.
Please note it's work in progress as I didn't manage today to thoroughly test it, but I expect to do it tomorrow morning.

With Regards,
Konrad Bańka 

 

 

  

 

With Regards,
Konrad Bańka 

 

 

  

Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Rajendra Prasad Mishra
 

Hi Taka, Steve,
   I am facing exactly the same problem as mentioned by Steve on Casablanca release. While doing "stop" LCM operation I get the 450 error.
As I understood from the the email chain, the problem was due to "capability-test" not passing. 

I see in the email thread that the error was somehow resolved. Can you please share the recipe for the fix.
I do not have a VNFC, hope that is not causing the problem. My vnf is the simple vLB (load balancer with DNS).

Here is the snippet of the log .
---------------------------------
2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | CONFIGTYPE=
2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vm-count=3
2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | skip-hypervisor-check=true
2019-07-22T12:26:38,994 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | request-action=Stop
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | input.action=Stop
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vnf.ipv4-oam-address=10.10.10.100
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | configuration-params=
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | VNFCNAME0=
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | template-name=
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vm[1].tenant-id=5a7c7f86fcaa418f83be664f921bf4ee
2019-07-22T12:26:38,995 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | getVnfcFunctionCodeForVserver()::vnfcFunctionCode=null
20ppc-config-data-services - 1.4.4 | processCapabilitiesForVMLevel() :: vnfcFunctionCode is not present in context!!!
      | 509 - appc-config-data-services - 1.4.4 | getCapability Successful
19-07-22T12:26:38,996 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | processCapabilitiesForVMLevel() :: vnfcFunctionCode is not present in context!!!
2019-07-22T12:26:38,996 | INFO  | appc-dispatcher-4 | ConfigResourceNode               | 509 - appc-config-data-services - 1.4.4 | getCapability Successful
.
.
.
2019-07-22T12:26:39,000 | INFO  | appc-dispatcher-4 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 47 (execute)
2019-07-22T12:26:39,011 | INFO  | appc-dispatcher-4 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome (success) not found, keys are { (failure)}
2019-07-22T12:26:39,011 | INFO  | appc-dispatcher-4 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome (Other) not found, keys are { (failure)}
2019-07-22T12:26:39,036 | INFO  | appc-dispatcher-4 | audit                            | 458 - appc-common-bundle - 1.4.4 | APPC0090A Operation "Stop" for VNF type "097d2826-1949-4ad8-ab4f-dc2e27e94022" from Source "SDNGP" with RequestID "386d0f72-5495-4a50-b7fc-7e4003d8335c" was started at "2019-07-22T12:26:37Z" and ended at "2019-07-22T12:26:39Z" with status code "450"
---------------------------------

thanks,
-RP

Re: Error while deploying APPC in ONAP #appc #deployment

Lathish
 

Did you check the safe_to_bootstrap value in docker nfs location of appc?

 

If it is 0, try to set it 1 in data0,data1,data2 and recreate the DB pod.

 

/Lathish

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Taka Cho via Lists.Onap.Org
Sent: Monday, July 22, 2019 3:14 PM
To: onap-discuss@...; prateekg099@...
Subject: Re: [onap-discuss] Error while deploying APPC in ONAP #appc #deployment

 

Hi,

 

I think it’s something is wrong in your NFS shared mount.

 

Taka

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Prateek Gupta
Sent: Monday, July 22, 2019 9:18 AM
To: onap-discuss@...
Subject: [onap-discuss] Error while deploying APPC in ONAP #appc #deployment

 

Error while bringing up the dev-appc-appc-db-0 component.

 

2019-07-22 17:18:21 140476023458048 [ERROR] WSREP: It may not be safe to bootstrap the cluster from this node. It was not the last one to leave the cluster and may not contain all the updates. To force cluster bootstrap with this node, edit the grastate.dat file manually and set safe_to_bootstrap to 1 .

2019-07-22 17:18:21 140476023458048 [ERROR] WSREP: wsrep::connect(gcomm://) failed: 7

2019-07-22 17:18:21 140476023458048 [ERROR] Aborting


Status of the pods:

root@onap-master:/home/onapmaster# kubectl get pods -n onap | grep appc

dev-appc-appc-0                                       0/2       Init:0/1           19         3h

dev-appc-appc-ansible-server-589cb48497-pxfr4         0/1       Init:Error         19         3h

dev-appc-appc-cdt-57d685d65c-wlt6s                    1/1       Running            0          3h

dev-appc-appc-db-0                                    0/1       CrashLoopBackOff   41         3h

dev-appc-appc-dgbuilder-768d9f4fb8-sng6k              0/1       Init:0/1           19         3h


Image we are using is :-    nexus3.onap.org:10001/adfinissygroup/k8s-mariadb-galera-centos:v003

If anyone faced the same issue please help.

 

Re: Error while deploying APPC in ONAP #appc #deployment

Taka Cho
 

Hi,

 

I think it’s something is wrong in your NFS shared mount.

 

Taka

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Prateek Gupta
Sent: Monday, July 22, 2019 9:18 AM
To: onap-discuss@...
Subject: [onap-discuss] Error while deploying APPC in ONAP #appc #deployment

 

Error while bringing up the dev-appc-appc-db-0 component.

 

2019-07-22 17:18:21 140476023458048 [ERROR] WSREP: It may not be safe to bootstrap the cluster from this node. It was not the last one to leave the cluster and may not contain all the updates. To force cluster bootstrap with this node, edit the grastate.dat file manually and set safe_to_bootstrap to 1 .

2019-07-22 17:18:21 140476023458048 [ERROR] WSREP: wsrep::connect(gcomm://) failed: 7

2019-07-22 17:18:21 140476023458048 [ERROR] Aborting


Status of the pods:

root@onap-master:/home/onapmaster# kubectl get pods -n onap | grep appc

dev-appc-appc-0                                       0/2       Init:0/1           19         3h

dev-appc-appc-ansible-server-589cb48497-pxfr4         0/1       Init:Error         19         3h

dev-appc-appc-cdt-57d685d65c-wlt6s                    1/1       Running            0          3h

dev-appc-appc-db-0                                    0/1       CrashLoopBackOff   41         3h

dev-appc-appc-dgbuilder-768d9f4fb8-sng6k              0/1       Init:0/1           19         3h


Image we are using is :-    nexus3.onap.org:10001/adfinissygroup/k8s-mariadb-galera-centos:v003

If anyone faced the same issue please help.

 

Error while deploying APPC in ONAP #appc #deployment

Prateek Gupta
 

Error while bringing up the dev-appc-appc-db-0 component.
 
2019-07-22 17:18:21 140476023458048 [ERROR] WSREP: It may not be safe to bootstrap the cluster from this node. It was not the last one to leave the cluster and may not contain all the updates. To force cluster bootstrap with this node, edit the grastate.dat file manually and set safe_to_bootstrap to 1 .
2019-07-22 17:18:21 140476023458048 [ERROR] WSREP: wsrep::connect(gcomm://) failed: 7
2019-07-22 17:18:21 140476023458048 [ERROR] Aborting

Status of the pods:
root@onap-master:/home/onapmaster# kubectl get pods -n onap | grep appc
dev-appc-appc-0                                       0/2       Init:0/1           19         3h
dev-appc-appc-ansible-server-589cb48497-pxfr4         0/1       Init:Error         19         3h
dev-appc-appc-cdt-57d685d65c-wlt6s                    1/1       Running            0          3h
dev-appc-appc-db-0                                    0/1       CrashLoopBackOff   41         3h
dev-appc-appc-dgbuilder-768d9f4fb8-sng6k              0/1       Init:0/1           19         3h

Image we are using is :-    nexus3.onap.org:10001/adfinissygroup/k8s-mariadb-galera-centos:v003

If anyone faced the same issue please help.
 

Re: [aai] Error while loading the graphadmin schema

Chandra
 

Hi Mahendra,
I can find the warning in the Cassandra logs at startup. Is there any specific configuration we are missing here?

WARN 13:13:15 Seed provider couldn't lookup host dev-aai-aai-cassandra-0.aai-cassandra
WARN 13:13:35 Seed provider couldn't lookup host dev-aai-aai-cassandra-1.aai-cassandra

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Chandra via Lists.Onap.Org
Sent: 22 July 2019 15:23
To: Mahendra Raghuwanshi <mahendra.raghuwanshi@...>; onap-discuss@...
Subject: Re: [onap-discuss] [aai] Error while loading the graphadmin schema

Hi Mahendra,
We were able to setup the Cassandra outside via Laodbalancer. However; there is Cassandraissue while loading the graphadmin schema with error as – We tried nodetool status.. seems all 3 nodes are well connected. Any more pointers to resolve this issue?


Exception is as follows:
com.netflix.astyanax.connectionpool.exceptions.PoolTimeoutException: PoolTimeoutException: [host=dev-aai-aai-cassandra-2.aai-cassandra(dev-aai-aai-cassandra-2.aai-cassandra):9160, latency=30001(30001), attempts=3]Timed out waiting for connection



From: Mahendra Raghuwanshi [mailto:mahendra.raghuwanshi@...]
Sent: 25 June 2019 11:06
To: Chandrashekhar Thakare <CT00548828@...<mailto:CT00548828@...>>; onap-discuss@...<mailto:onap-discuss@...>
Subject: Re: [onap-discuss] [aai] Error while loading the graphadmin schema

Hi Chandra,

To allow the communication among the statefulset Pods (in case of Cassandra we need all the Nodes talking to each other), we need headless service which means clusterIP as None (old service.yaml contains this for aai-cassandra). This allows each Pod of the statefulset to be addressed using <PodName>.<serviceName> as FQDN and accessible explicitly.
You may have to remove the clusterIP: None from service.yaml but then cassandra cluster itself would stop working as seeds will not be available as we need to address each node.
To allow exposing the cassandra cluster outside, you may want to create another service which can be a LoadBalancer or NodePort.


Always run the "nodetool status" in each of the cluster node to validate if they are able to see rest of the nodes available in the cluster.


Thx,
Mahendra
============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

Re: [POLICY] Policy creation via GUI failed.

Ram
 

Dear PAMELA L,

Please find the following steps to re-create this policy

Prerequisite: 
Dictionary has to be created with ClosedLoopControlName and I have attached the drools file the one which is used in environmenet.

Step: Create a policy using below parameters

image.png

Please use below content for controlLoopYaml and closedLoopControlName 

controlLoopYaml: ControlLoop-CCVPN-2179b738-fd36-4843-a71a-a8c24c70c33b

closedLoopControlName: controlLoop%3A%0A%20%20version%3A%202.0.0%0A%20%20controlLoopName%3A%20ControlLoop-CCVPN-2179b738-fd36-4843-a71a-a8c24c70c33b%0A%20%20trigger_policy%3A%20unique-policy-id-16-NetworkSlice%0A%20%20timeout%3A%203600%0A%20%20abatement%3A%20false%0A%20%0Apolicies%3A%0A%20%20-%20id%3A%20unique-policy-id-16-NetworkSlice%0A%20%20%20%20name%3A%20Network%20Slice%0A%20%20%20%20description%3A%0A%20%20%20%20actor%3A%20SDNC%0A%20%20%20%20recipe%3A%20NetworkSlice%0A%20%20%20%20target%3A%0A%20%20%20%20%20%20type%3A%20VM%0A%20%20%20%20retry%3A%203%0A%20%20%20%20timeout%3A%201200%0A%20%20%20%20success%3A%20final_success%0A%20%20%20%20failure%3A%20final_failure%0A%20%20%20%20failure_timeout%3A%20final_failure_timeout%0A%20%20%20%20failure_retries%3A%20final_failure_retries%0A%20%20%20%20failure_exception%3A%20final_failure_exception%0A%20%20%20%20failure_guard%3A%20final_failure_guard

Step 2: Observed issue when try to push the above created policy into default pdp group

Note: If any steps are missed or further queries, Kindly let us know

Thanks,
Rama

On Mon, Jul 22, 2019 at 4:59 PM DRAGOSH, PAMELA L (PAM) <pdragosh@...> wrote:

Rama,

 

I don’t see how we can help you without more details. Perhaps you can show what policy you created? And the steps to re-create this?

 

Regards,

 

Pam

 

From: Rama Subba Reddy <rama.manthu455@...>
Date: Monday, July 22, 2019 at 4:45 AM
To: "onap-discuss@..." <onap-discuss@...>, "DRAGOSH, PAMELA L (PAM)" <pdragosh@...>, "HERNANDEZ-HERRERO, JORGE" <jh1730@...>
Cc: "chenchuanyu@..." <chenchuanyu@...>, "gaurav.agrawal@..." <gaurav.agrawal@...>, "vidyashree.rama@..." <vidyashree.rama@...>, "zhoujun8@..." <zhoujun8@...>
Subject: Fwd: [onap-discuss][POLICY] Policy creation via GUI failed.

 

Hi All,

 

Kindly help to resolve this issue

Issue: Creation of policy is success but however while push policy getting following error " XML Parsing Error: not well-formed"

 

mage.png

 

Thanks,

Rama

Re: [POLICY] Policy creation via GUI failed.

Pamela Dragosh
 

Rama,

 

I don’t see how we can help you without more details. Perhaps you can show what policy you created? And the steps to re-create this?

 

Regards,

 

Pam

 

From: Rama Subba Reddy <rama.manthu455@...>
Date: Monday, July 22, 2019 at 4:45 AM
To: "onap-discuss@..." <onap-discuss@...>, "DRAGOSH, PAMELA L (PAM)" <pdragosh@...>, "HERNANDEZ-HERRERO, JORGE" <jh1730@...>
Cc: "chenchuanyu@..." <chenchuanyu@...>, "gaurav.agrawal@..." <gaurav.agrawal@...>, "vidyashree.rama@..." <vidyashree.rama@...>, "zhoujun8@..." <zhoujun8@...>
Subject: Fwd: [onap-discuss][POLICY] Policy creation via GUI failed.

 

Hi All,

 

Kindly help to resolve this issue

Issue: Creation of policy is success but however while push policy getting following error " XML Parsing Error: not well-formed"

 

mage.png

 

Thanks,

Rama

Re: [aai] Error while loading the graphadmin schema

Chandra
 

Hi Mahendra,
We were able to setup the Cassandra outside via Laodbalancer. However; there is Cassandraissue while loading the graphadmin schema with error as – We tried nodetool status.. seems all 3 nodes are well connected. Any more pointers to resolve this issue?


Exception is as follows:
com.netflix.astyanax.connectionpool.exceptions.PoolTimeoutException: PoolTimeoutException: [host=dev-aai-aai-cassandra-2.aai-cassandra(dev-aai-aai-cassandra-2.aai-cassandra):9160, latency=30001(30001), attempts=3]Timed out waiting for connection



From: Mahendra Raghuwanshi [mailto:mahendra.raghuwanshi@...]
Sent: 25 June 2019 11:06
To: Chandrashekhar Thakare <CT00548828@...>; onap-discuss@...
Subject: Re: [onap-discuss] [aai] Error while loading the graphadmin schema

Hi Chandra,

To allow the communication among the statefulset Pods (in case of Cassandra we need all the Nodes talking to each other), we need headless service which means clusterIP as None (old service.yaml contains this for aai-cassandra). This allows each Pod of the statefulset to be addressed using <PodName>.<serviceName> as FQDN and accessible explicitly.
You may have to remove the clusterIP: None from service.yaml but then cassandra cluster itself would stop working as seeds will not be available as we need to address each node.
To allow exposing the cassandra cluster outside, you may want to create another service which can be a LoadBalancer or NodePort.


Always run the "nodetool status" in each of the cluster node to validate if they are able to see rest of the nodes available in the cluster.


Thx,
Mahendra
============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

Re: MD-SAL Data migration Casablanca to Dublin #sdnc

Piyush Garg
 

Thanks Dan.

 

Regards,

Piyush

 

From: TIMONEY, DAN <dt5972@...>
Sent: Friday, July 19, 2019 11:00 PM
To: onap-discuss@...; Piyush Garg <Piyush.Garg1@...>
Subject: Re: [onap-discuss] MD-SAL Data migration Casablanca to Dublin #sdnc

 

Piyush,

 

Here’s a link to the Gerrit change that updated those enum values:

 

https://gerrit.onap.org/r/c/sdnc/northbound/+/79746

 

Those are used for the CCVPN use case, and that particular change removed those somewhat generic request action values and replaced them with more granular values (e.g CreateSDWANLanPortInstance instead of CreateSDWANAttachmentInstance).  So, I don’t know that there is necessarily a one to one mapping – you’d need to look at other fields in the request to figure out if the “attachment” being added was a port vs a site, for example.  However, since that enum only applies to the request type itself, I’m not sure that it’s used in any of the data stored in MD-SAL.

 

Prakash – I noticed that change was yours.  Maybe you might have more insights as well?

 

Dan

 

Dan Timoney

Principal Technical Staff Member

AT&T

Email : dtimoney@...

Office : +1 (732) 420-3226

Mobile : +1 (201) 960-1211

200 S Laurel Ave, Rm E2-2A03

Middletown, NJ 08873

 

From: onap-discuss <onap-discuss@...> on behalf of Piyush Garg <piyush.garg1@...>
Reply-To: onap-discuss <onap-discuss@...>, "piyush.garg1@..." <piyush.garg1@...>
Date: Thursday, July 18, 2019 at 10:45 AM
To: onap-discuss <onap-discuss@...>
Subject: [onap-discuss] MD-SAL Data migration Casablanca to Dublin #sdnc

 

Hi,

I was analysis the yang models for SDNC to see a impact of data migration from Casablanca to Dublin release. Below are the analysis details and some queries:
- VNF-API yang: No change in the model and hence no impact in the data migration
- GENERIC-RESOURCE-API yang: Lots of changes in the model but looks like only thing that can impact the migration is the removal of following enums from the "request-action" and "last-action":
enum "CreateSDWANConnectivityInstance";
enum "ActivateSDWANConnectivityInstance";
enum "DeactivateSDWANConnectivityInstance";
enum "DeleteSDWANConnectivityInstance";
enum "CreateSDWANAttachmentInstance";
enum "ActivateSDWANAttachmentInstance";
enum "DeactivateSDWANAttachmentInstance";
enum "DeleteSDWANAttachmentInstance";


Can you confirm if this understanding is correct or not ?

Also, can you please help me understand how it should be handled if we have any such data where above actions were used ? Like if these actions should be updated with some other action!

Regards,
Piyush

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service

[dcaegen2] docker image dependency chart

Paul Vaduva
 

Hi dcaegen2 team

 

I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the dcaegen2 project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for dcaegen2 porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

You can see the list of docker images dependencies for each project in a roughly form like this:

1 --> 2 --> 3 ... --> n

where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image.

The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart.

As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well).

 

Thank you,

Paul


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.

[logging] docker image dependency chart

Paul Vaduva
 

Hi logging team

 

I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the logging project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for logging porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

You can see the list of docker images dependencies for each project in a roughly form like this:

1 --> 2 --> 3 ... --> n

where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image.

The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart.

As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well).

 

Thank you,

Paul


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.

[POLICY] Policy creation via GUI failed.

Ram
 

Hi All,

Kindly help to resolve this issue
Issue: Creation of policy is success but however while push policy getting following error " XML Parsing Error: not well-formed"

image.png

Thanks,
Rama

Re: [modeling] docker image dependency chart

Paul Vaduva
 

Thank you Yuanhong

 

Best Regards,

Paul

 

From: dengyuanhong <dengyuanhong@...>
Sent: Monday, July 22, 2019 11:20 AM
To: onap-discuss@...; Paul Vaduva <Paul.Vaduva@...>
Cc: denghui02@...; 'Jessica Wagantall' <jwagantall@...>; 'Jim Baker' <jbaker@...>; 'Kenny Paul' <kpaul@...>
Subject: Re: [onap-discuss][modeling] docker image dependency chart

 

Hi Paul,

 

I have edited the information for modeling and changed the image from python2-alpine to python3.6-alpine.

 

Thanks and regards,

Yuanhong

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Paul Vaduva
Sent: 2019719 19:12
To: onap-discuss@...
Cc: denghui02@...; Jessica Wagantall; Jim Baker; Kenny Paul
Subject: [onap-discuss][modeling] docker image dependency chart

 

Hi modeling team

 

I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the modeling project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for modeling porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

You can see the list of docker images dependencies for each project in a roughly form like this:

1 --> 2 --> 3 ... --> n

where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image.

The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart.

As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well).

 

Thank you,

Paul


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.

Re: [modeling] docker image dependency chart

Deng Yuanhong
 

Hi Paul,

 

I have edited the information for modeling and changed the image from python2-alpine to python3.6-alpine.

 

Thanks and regards,

Yuanhong

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Paul Vaduva
Sent: 2019719 19:12
To: onap-discuss@...
Cc: denghui02@...; Jessica Wagantall; Jim Baker; Kenny Paul
Subject: [onap-discuss][modeling] docker image dependency chart

 

Hi modeling team

 

I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the modeling project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for modeling porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

You can see the list of docker images dependencies for each project in a roughly form like this:

1 --> 2 --> 3 ... --> n

where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image.

The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart.

As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well).

 

Thank you,

Paul


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.

Re: SDNC REST Call to 3rd Party Controller #sdnc

shashikath
 

Hi Minsang,

Import server’s certificate to the truststore file to resolve this issue.

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of minsang.yoon@...
Sent: 2019
721 7:28
To: onap-discuss@...
Subject: [onap-discuss] SDNC REST Call to 3rd Party Controller #sdnc

 

When I try to send REST request to 3rd party controller, I face the issue like below. 
I saw the JIRA ticket is open for the same case and closed but still having the same issue. Anyone know how to solve this problem?

2019-07-21T00:41:01,861 | ERROR | qtp1035549374-64 | RestapiCallNode                  | 235 - org.onap.ccsdk.sli.plugins.restapi-call-node-provider - 0.3.3 | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=mef-evc-vnf-topology-operation-activate, mode=sync, version=1.1.1, md5sum=c8ee81c6c0149b660fdf0f1f43b25ec5] - 38 (execute) | Error sending the request: Exception while posting http request to client javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

org.onap.ccsdk.sli.core.sli.SvcLogicException: Exception while posting http request to client javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendHttpRequest(RestapiCallNode.java:657) [235:org.onap.ccsdk.sli.plugins.restapi-call-node-provider:0.3.3]

        at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendRequest(RestapiCallNode.java:309) [235:org.onap.ccsdk.sli.plugins.restapi-call-node-provider:0.3.3]

        at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendRequest(RestapiCallNode.java:287) [235:org.onap.ccsdk.sli.plugins.restapi-call-node-provider:0.3.3]

        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) ~[?:?]

        at org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:54) [96:org.apache.aries.proxy:1.1.1]

        at org.apache.aries.proxy.impl.ProxyHandler.invoke(ProxyHandler.java:119) [96:org.apache.aries.proxy:1.1.1]

        at org.onap.ccsdk.sli.plugins.restapicall.$RestapiCallNode719527416.sendRequest(Unknown Source) [235:org.onap.ccsdk.sli.plugins.restapi-call-node-provider:0.3.3]

        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) ~[?:?]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:188) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:188) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:158) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:128) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:188) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:188) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:188) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:158) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:224) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:202) [222:org.onap.ccsdk.sli.core.sli-provider:0.3.3]

        at Proxye46bbf1e_41fe_4298_b0f8_ec7d35fbc311.execute(Unknown Source) [?:?]

        at Proxyac5aa1aa_e700_4972_88ed_e9f7690f0a58.execute(Unknown Source) [?:?]

        at org.onap.sdnc.northbound.GenericResourceApiSvcLogicServiceClient.execute(GenericResourceApiSvcLogicServiceClient.java:73) [441:org.onap.sdnc.northbound.generic-resource-api-provider:1.4.3]

        at org.onap.sdnc.northbound.GenericResourceApiProvider.tryGetProperties(GenericResourceApiProvider.java:754) [441:org.onap.sdnc.northbound.generic-resource-api-provider:1.4.3]

        at org.onap.sdnc.northbound.GenericResourceApiProvider.vnfTopologyOperation(GenericResourceApiProvider.java:866) [441:org.onap.sdnc.northbound.generic-resource-api-provider:1.4.3]

        at org.opendaylight.yangtools.yang.binding.util.RpcMethodInvokerWithInput.invokeOn(RpcMethodInvokerWithInput.java:32) [343:org.opendaylight.mdsal.yang-binding:0.12.3]

        at org.opendaylight.yangtools.yang.binding.util.AbstractMappedRpcInvoker.invokeRpc(AbstractMappedRpcInvoker.java:53) [343:org.opendaylight.mdsal.yang-binding:0.12.3]

        at org.opendaylight.controller.md.sal.binding.impl.BindingDOMRpcImplementationAdapter.invoke(BindingDOMRpcImplementationAdapter.java:83) [267:org.opendaylight.controller.sal-binding-broker-impl:1.7.3]

        at org.opendaylight.controller.md.sal.binding.impl.BindingDOMRpcImplementationAdapter.invokeRpc(BindingDOMRpcImplementationAdapter.java:70) [267:org.opendaylight.controller.sal-binding-broker-impl:1.7.3]

        at org.opendaylight.controller.md.sal.dom.broker.impl.GlobalDOMRpcRoutingTableEntry.invokeRpc(GlobalDOMRpcRoutingTableEntry.java:41) [270:org.opendaylight.controller.sal-broker-impl:1.7.3]

        at org.opendaylight.controller.md.sal.dom.broker.impl.DOMRpcRoutingTable.invokeRpc(DOMRpcRoutingTable.java:178) [270:org.opendaylight.controller.sal-broker-impl:1.7.3]

        at org.opendaylight.controller.md.sal.dom.broker.impl.DOMRpcRouter.invokeRpc(DOMRpcRouter.java:102) [270:org.opendaylight.controller.sal-broker-impl:1.7.3]

        at Proxy7f188c87_edfb_476a_a482_0bf1d0697f19.invokeRpc(Unknown Source) [?:?]

        at Proxybfd8c1a1_d69e_4408_8a93_5b5e7340ac71.invokeRpc(Unknown Source) [?:?]

        at org.opendaylight.netconf.sal.restconf.impl.BrokerFacade.invokeRpc(BrokerFacade.java:523) [349:org.opendaylight.netconf.restconf-nb-bierman02:1.7.3]

        at org.opendaylight.netconf.sal.restconf.impl.RestconfImpl.invokeRpc(RestconfImpl.java:463) [349:org.opendaylight.netconf.restconf-nb-bierman02:1.7.3]

        at org.opendaylight.netconf.sal.restconf.impl.StatisticsRestconfServiceWrapper.invokeRpc(StatisticsRestconfServiceWrapper.java:86) [349:org.opendaylight.netconf.restconf-nb-bierman02:1.7.3]

        at org.opendaylight.netconf.sal.rest.impl.RestconfCompositeWrapper.invokeRpc(RestconfCompositeWrapper.java:64) [349:org.opendaylight.netconf.restconf-nb-bierman02:1.7.3]

        at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source) ~[?:?]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]

        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]

        at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.uri.rules.ResourceObjectRule.accept(ResourceObjectRule.java:100) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) [17:com.sun.jersey.jersey-server:1.19.4]

        at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) [18:com.sun.jersey.servlet:1.19.4]

        at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) [18:com.sun.jersey.servlet:1.19.4]

        at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) [18:com.sun.jersey.servlet:1.19.4]

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [77:javax.servlet-api:3.1.0]

        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:205) [183:org.eclipse.jetty.websocket.server:9.3.21.v20170918]

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:308) [174:org.eclipse.jetty.servlets:9.3.21.v20170918]

        at org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:262) [174:org.eclipse.jetty.servlets:9.3.21.v20170918]

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:51) [174:org.eclipse.jetty.servlets:9.3.21.v20170918]

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.opendaylight.aaa.filterchain.filters.CustomFilterAdapter.doFilter(CustomFilterAdapter.java:103) [244:org.opendaylight.aaa.filterchain:0.7.3]

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:61) [152:org.apache.shiro.web:1.3.2]

        at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108) [152:org.apache.shiro.web:1.3.2]

        at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137) [152:org.apache.shiro.web:1.3.2]

        at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125) [152:org.apache.shiro.web:1.3.2]

        at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66) [152:org.apache.shiro.web:1.3.2]

        at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449) [152:org.apache.shiro.web:1.3.2]

        at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365) [152:org.apache.shiro.web:1.3.2]

        at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90) [151:org.apache.shiro.core:1.3.2]

        at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83) [151:org.apache.shiro.core:1.3.2]

        at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:383) [151:org.apache.shiro.core:1.3.2]

        at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362) [152:org.apache.shiro.web:1.3.2]

        at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125) [152:org.apache.shiro.web:1.3.2]

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [385:org.ops4j.pax.web.pax-web-jetty:6.0.9]

        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [170:org.eclipse.jetty.security:9.3.21.v20170918]

        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:284) [385:org.ops4j.pax.web.pax-web-jetty:6.0.9]

        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [173:org.eclipse.jetty.servlet:9.3.21.v20170918]

        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [385:org.ops4j.pax.web.pax-web-jetty:6.0.9]

        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.eclipse.jetty.server.Server.handle(Server.java:534) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [172:org.eclipse.jetty.server:9.3.21.v20170918]

        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) [164:org.eclipse.jetty.io:9.3.21.v20170918]

        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) [164:org.eclipse.jetty.io:9.3.21.v20170918]

        at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [164:org.eclipse.jetty.io:9.3.21.v20170918]

        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [175:org.eclipse.jetty.util:9.3.21.v20170918]

        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [175:org.eclipse.jetty.util:9.3.21.v20170918]

        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [175:org.eclipse.jetty.util:9.3.21.v20170918]

        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [175:org.eclipse.jetty.util:9.3.21.v20170918]

        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [175:org.eclipse.jetty.util:9.3.21.v20170918]

        at java.lang.Thread.run(Thread.java:748) [?:?]

Caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:284) ~[?:?]

        at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:278) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$0(JerseyInvocation.java:753) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:316) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:298) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:229) ~[?:?]

        at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:414) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:752) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:445) ~[?:?]

        at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendHttpRequest(RestapiCallNode.java:654) ~[?:?]

        ... 113 more

Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946) ~[?:?]

        at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316) ~[?:?]

        at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310) ~[?:?]

        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639) ~[?:?]

        at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223) ~[?:?]

        at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) ~[?:?]

        at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) ~[?:?]

        at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) ~[?:?]

        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) ~[?:?]

        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1334) ~[?:?]

        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1309) ~[?:?]

        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:259) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector.lambda$_apply$0(HttpUrlConnector.java:382) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.commitStream(CommittingOutputStream.java:195) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.commitStream(CommittingOutputStream.java:189) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.write(CommittingOutputStream.java:223) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$UnCloseableOutputStream.write(WriterInterceptorExecutor.java:300) ~[?:?]

        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) ~[?:?]

        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) ~[?:?]

        at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) ~[?:?]

        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) ~[?:?]

        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) ~[?:?]

        at org.glassfish.jersey.message.internal.ReaderWriter.writeToAsString(ReaderWriter.java:194) ~[?:?]

        at org.glassfish.jersey.message.internal.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:131) ~[?:?]

        at org.glassfish.jersey.message.internal.StringMessageProvider.writeTo(StringMessageProvider.java:100) ~[?:?]

        at org.glassfish.jersey.message.internal.StringMessageProvider.writeTo(StringMessageProvider.java:60) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.invokeWriteTo(WriterInterceptorExecutor.java:266) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.aroundWriteTo(WriterInterceptorExecutor.java:251) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:163) ~[?:?]

        at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1135) ~[?:?]

        at org.glassfish.jersey.client.ClientRequest.doWriteEntity(ClientRequest.java:516) ~[?:?]

        at org.glassfish.jersey.client.ClientRequest.writeEntity(ClientRequest.java:498) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector._apply(HttpUrlConnector.java:384) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:282) ~[?:?]

        at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:278) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$0(JerseyInvocation.java:753) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:316) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:298) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:229) ~[?:?]

        at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:414) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:752) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:445) ~[?:?]

        at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendHttpRequest(RestapiCallNode.java:654) ~[?:?]

        ... 113 more

Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:397) ~[?:?]

        at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302) ~[?:?]

        at sun.security.validator.Validator.validate(Validator.java:262) ~[?:?]

        at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) ~[?:?]

        at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) ~[?:?]

        at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) ~[?:?]

        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1621) ~[?:?]

        at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223) ~[?:?]

        at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) ~[?:?]

        at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) ~[?:?]

        at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) ~[?:?]

        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) ~[?:?]

        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1334) ~[?:?]

        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1309) ~[?:?]

        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:259) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector.lambda$_apply$0(HttpUrlConnector.java:382) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.commitStream(CommittingOutputStream.java:195) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.commitStream(CommittingOutputStream.java:189) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.write(CommittingOutputStream.java:223) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$UnCloseableOutputStream.write(WriterInterceptorExecutor.java:300) ~[?:?]

        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) ~[?:?]

        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) ~[?:?]

        at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) ~[?:?]

        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) ~[?:?]

        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) ~[?:?]

        at org.glassfish.jersey.message.internal.ReaderWriter.writeToAsString(ReaderWriter.java:194) ~[?:?]

        at org.glassfish.jersey.message.internal.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:131) ~[?:?]

        at org.glassfish.jersey.message.internal.StringMessageProvider.writeTo(StringMessageProvider.java:100) ~[?:?]

        at org.glassfish.jersey.message.internal.StringMessageProvider.writeTo(StringMessageProvider.java:60) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.invokeWriteTo(WriterInterceptorExecutor.java:266) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.aroundWriteTo(WriterInterceptorExecutor.java:251) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:163) ~[?:?]

        at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1135) ~[?:?]

        at org.glassfish.jersey.client.ClientRequest.doWriteEntity(ClientRequest.java:516) ~[?:?]

        at org.glassfish.jersey.client.ClientRequest.writeEntity(ClientRequest.java:498) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector._apply(HttpUrlConnector.java:384) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:282) ~[?:?]

        at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:278) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$0(JerseyInvocation.java:753) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:316) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:298) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:229) ~[?:?]

        at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:414) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:752) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:445) ~[?:?]

        at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendHttpRequest(RestapiCallNode.java:654) ~[?:?]

        ... 113 more

Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) ~[?:?]

        at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) ~[?:?]

        at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) ~[?:?]

        at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:392) ~[?:?]

        at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302) ~[?:?]

        at sun.security.validator.Validator.validate(Validator.java:262) ~[?:?]

        at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) ~[?:?]

        at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) ~[?:?]

        at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) ~[?:?]

        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1621) ~[?:?]

        at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223) ~[?:?]

        at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) ~[?:?]

        at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) ~[?:?]

        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) ~[?:?]

        at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) ~[?:?]

        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) ~[?:?]

        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1334) ~[?:?]

        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1309) ~[?:?]

        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:259) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector.lambda$_apply$0(HttpUrlConnector.java:382) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.commitStream(CommittingOutputStream.java:195) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.commitStream(CommittingOutputStream.java:189) ~[?:?]

        at org.glassfish.jersey.message.internal.CommittingOutputStream.write(CommittingOutputStream.java:223) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$UnCloseableOutputStream.write(WriterInterceptorExecutor.java:300) ~[?:?]

        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) ~[?:?]

        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) ~[?:?]

        at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) ~[?:?]

        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) ~[?:?]

        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) ~[?:?]

        at org.glassfish.jersey.message.internal.ReaderWriter.writeToAsString(ReaderWriter.java:194) ~[?:?]

        at org.glassfish.jersey.message.internal.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:131) ~[?:?]

        at org.glassfish.jersey.message.internal.StringMessageProvider.writeTo(StringMessageProvider.java:100) ~[?:?]

        at org.glassfish.jersey.message.internal.StringMessageProvider.writeTo(StringMessageProvider.java:60) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.invokeWriteTo(WriterInterceptorExecutor.java:266) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.aroundWriteTo(WriterInterceptorExecutor.java:251) ~[?:?]

        at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:163) ~[?:?]

        at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1135) ~[?:?]

        at org.glassfish.jersey.client.ClientRequest.doWriteEntity(ClientRequest.java:516) ~[?:?]

        at org.glassfish.jersey.client.ClientRequest.writeEntity(ClientRequest.java:498) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector._apply(HttpUrlConnector.java:384) ~[?:?]

        at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:282) ~[?:?]

        at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:278) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$0(JerseyInvocation.java:753) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:316) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:298) ~[?:?]

        at org.glassfish.jersey.internal.Errors.process(Errors.java:229) ~[?:?]

        at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:414) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:752) ~[?:?]

        at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:445) ~[?:?]

        at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendHttpRequest(RestapiCallNode.java:654) ~[?:?]

        ... 113 more