If you look inside the guilin-sdnc-2 you will like see opendaylight errors in 
the karaf.log.

I would delete the pods that have shared errors in karaf.log and make sure 
healthcheck for sdnc passes.

there are methods to see cluster health inside opendaylight but I'm not 
familiar enough with the command from the opendaylight documentation.

brian


From: Narayanasetty Sowmya <[email protected]>
Sent: Friday, December 11, 2020 7:39 AM
To: FREEMAN, BRIAN D <[email protected]>; [email protected]
Cc: Velugubantla Praveen <[email protected]>
Subject: Re: Not able to deploy a VNF through GR-API in guilin

Hi BRIAN,

Thanks for your response,

Here is the state of SDNC & SDNR pods in our environment,

root@guilin-nfs:~/oom/kubernetes/robot# kubectl get pods | grep sdnc
guilin-sdnc-0                                         2/2     Running      0    
      9d
guilin-sdnc-1                                         2/2     Running      0    
      9d
guilin-sdnc-2                                         2/2     Running      0    
      9d
guilin-sdnc-ansible-server-58c4fdc4c9-mg4qv           1/1     Running      0    
      9d
guilin-sdnc-db-0                                      1/1     Running      0    
      9d
guilin-sdnc-dbinit-job-6pkjq                          0/1     Completed    0    
      9d
guilin-sdnc-dgbuilder-7d69754bfc-ct2vp                1/1     Running      0    
      9d
guilin-sdnc-dmaap-listener-65687bf5f-kcf62            1/1     Running      0    
      9d
guilin-sdnc-sdnrdb-init-job-jstkg                     0/1     Completed    0    
      9d
guilin-sdnc-sdnrdb-init-job-stcwp                     0/1     Init:Error   0    
      9d
guilin-sdnc-ueb-listener-5d69799658-8bd4p             1/1     Running      0    
      9d
guilin-sdnc-web-7fcd558c58-zwkzs                      1/1     Running      0    
      9d
guilin-so-sdnc-adapter-6fb55759c8-7m7qr               2/2     Running      0    
      9d
root@guilin-nfs:~/oom/kubernetes/robot#

******************************************************************************************************************

root@guilin-nfs:~/oom/kubernetes/robot# kubectl get pods | grep sdnr
guilin-sdnc-sdnrdb-init-job-ccf4r                     0/1     Init:Error   0    
      9d
guilin-sdnc-sdnrdb-init-job-jstkg                     0/1     Completed    0    
      9d
guilin-sdnc-sdnrdb-init-job-stcwp                     0/1     Init:Error   0    
      9d
guilin-sdnrdb-coordinating-only-6964b89b5b-vph8f      2/2     Running      0    
      9d
guilin-sdnrdb-master-0                                1/1     Running      0    
      9d
guilin-sdnrdb-master-1                                1/1     Running      0    
      9d
guilin-sdnrdb-master-2                                1/1     Running      0    
      9d


As seems all the containers are in good state, Is the deletion of that pod will 
solve the problem ?

Regards,
Sowmya

________________________________
From: FREEMAN, BRIAN D <[email protected]<mailto:[email protected]>>
Sent: 11 December 2020 17:54
To: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>>; 
Narayanasetty Sowmya 
<[email protected]<mailto:[email protected]>>
Cc: Velugubantla Praveen 
<[email protected]<mailto:[email protected]>>
Subject: RE: Not able to deploy a VNF through GR-API in guilin


Sounds like one of your sdnc containers is down (perhaps dev-sdnc-2).



kubectl -n onap get pod | grep sdnc



Sdnc failing healthcheck means you won't be able to deploy a VNF anyway.



I'd restart the failed sdnc container :

kubectl -n onap delete pod dev-sdnc-0



since it looks like the containers are either network isolated or one 
opendaylight container is  not responding to the AKKA cluster health check 
messages.



brian







From: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>> On Behalf Of 
Narayanasetty Sowmya
Sent: Friday, December 11, 2020 3:39 AM
To: [email protected]<mailto:[email protected]>
Cc: Velugubantla Praveen 
<[email protected]<mailto:[email protected]>>
Subject: [onap-discuss] Not able to deploy a VNF through GR-API in guilin



Hi Team,



I am trying to deploy a vnf using gr-api by using the python scripts. But I am 
facing an error as follows:



"response-message": "TransactionCommitFailedException{message=canCommit 
encountered an unexpected failure, errorList=[RpcError [message=canCommit 
encountered an unexpected failure, severity=ERROR, errorType=APPLICATION, 
tag=operation-failed, applicationTag=null, info=null, 
cause=akka.pattern.AskTimeoutException: Ask timed out on 
[ActorSelection[Anchor(akka://opendaylight-cluster-data/), 
Path(/user/shardmanager-config/member-3-shard-default-config#-1175421278)]] 
after [120000 ms]. Message of type 
[org.opendaylight.controller.cluster.datastore.messages.ReadyLocalTransaction]. 
A typical reason for `AskTimeoutException` is that the recipient actor didn't 
send a reply.]]}"



And in my Guilin setup, HealthCheck of enhanced sdnc is failing.



PFA log of the so-sdnc adapter.



Any inputs on this would help me resolve my issue.



Thanks and Regards,

Sowmya









L&T Technology Services Ltd

www.LTTS.com<https://urldefense.com/v3/__https:/ind01.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__http*3A*2Fwww.LTTS.com__*3B!!BhdT!1Mg16-t-3L-1lkjU_Cg3R_Da7gUg-BKFNNqelZht65qxoaMiQxIO8xT5Zgw7BF4*24&data=04*7C01*7Cnarayanasetty.sowmya*40ltts.com*7C16586f7aea364dc7395e08d89dcfc8a3*7C311b33788e8a4b5ea33fe80a3d8ba60a*7C0*7C0*7C637432863038285385*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=FFIqW*2FHV4bKntUPor*2B7bng5lzuc5RhylKoynFMVWizg*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!BhdT!y-gQboiFoUwOucdNF919Xds2yFAv0SUtiyW0_I_iWHVvYgadshYa8_OtELUEGqY$>

L&T Technology Services Limited (LTTS) is committed to safeguard your data 
privacy. For more information to view our commitment towards data privacy under 
GDPR, please visit the privacy policy on our website 
www.Ltts.com<https://urldefense.com/v3/__https:/ind01.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__http*3A*2Fwww.Ltts.com__*3B!!BhdT!1Mg16-t-3L-1lkjU_Cg3R_Da7gUg-BKFNNqelZht65qxoaMiQxIO8xT5YmzWFqo*24&data=04*7C01*7Cnarayanasetty.sowmya*40ltts.com*7C16586f7aea364dc7395e08d89dcfc8a3*7C311b33788e8a4b5ea33fe80a3d8ba60a*7C0*7C0*7C637432863038295378*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=1FMAps7KOkjh*2BboeByJiAZM3MDRrySR0g7uwfrVUD8g*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!BhdT!y-gQboiFoUwOucdNF919Xds2yFAv0SUtiyW0_I_iWHVvYgadshYa8_OtCSmEzOg$>.
 This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.



L&T Technology Services Ltd

www.LTTS.com<https://urldefense.com/v3/__http:/www.LTTS.com__;!!BhdT!y-gQboiFoUwOucdNF919Xds2yFAv0SUtiyW0_I_iWHVvYgadshYa8_Ot5LFXvFM$>

L&T Technology Services Limited (LTTS) is committed to safeguard your data 
privacy. For more information to view our commitment towards data privacy under 
GDPR, please visit the privacy policy on our website 
www.Ltts.com<https://urldefense.com/v3/__http:/www.Ltts.com__;!!BhdT!y-gQboiFoUwOucdNF919Xds2yFAv0SUtiyW0_I_iWHVvYgadshYa8_Oty3HW4wc$>.
 This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22619): https://lists.onap.org/g/onap-discuss/message/22619
Mute This Topic: https://lists.onap.org/mt/78875217/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to