Hi Team, I am facing an issue with SDNC Pre-load. Since VNF-API is deprecated in Guilin, we should use GR-API. I am getting the below error when I issue a POST request. Any leads to resolve this issue

#sdnc

Hello All, on the ONAP Guilin version, I get this error at preload stage. Any ideas what might cause this? curl -k -X POST https://sdnc.api.simpledemo.onap.org:30267/restconf/operations/GENERIC-RESOUR

#sdnc

Hey Paulo, I was indeed able to fix it. The problem with my deployment was that I was directly changing the *testing flag of contrib in the onap/values.yaml to "true" instead of toggling addTestingCom

#sdnc #honolulu

Hi, Getting the same issue. Did you find any workaround for this? Thanks,

#sdnc #honolulu

Is the platform component enabled in the deployment? Based on this that seems to be the problem since oom-cert-service pod seems to be not deployed. If it's not enabled, try deploying it and restartin

#sdnc

Hey everyone, I'm trying to deploy Honolulu charts and facing a problem with SDNC components. The sdnc-0 pod is stuck in a crashloopbackoff state when it gets to the certs-init container. I have come

#sdnc #honolulu

Hi All, When deploying the ONAP Honolulu release, SDNC pods are not coming up and CDS Health check is also Failing. aarna@anod-master:~/oom/kubernetes/robot$ ./ete-k8s.sh onap health ++ export NAMESPA

#sdnc

A test on my system it is working fine: helm version version.BuildInfo{Version:"v3.3.4", GitCommit:"a61ce5633af99708171414353ed49547cf05013d", GitTreeState:"clean", GoVersion:"go1.14.9"} kubectl versi

#sdnc #sdnr

Thank you for the response. AAF pods were running fine. I think there is a issue in fetching the certs [root@onap-controller kubernetes]# kubectl logs -n onap dev-sdnrdb-coordinating-only-85cb897d86-j

#sdnc #sdnr

dev-sdnc-sdnrdb-init-job-ng8lf 0/1 Completed 0 169m <-- this job should not be completed because it is waiting for onap-sdnrdb-coordinating-only-9cfb74b56-2vmf6 Is aaf working correctly? all pods up a

#sdnc #sdnr

Hi All, I am deploying ONAP Guilin latest charts. SDNC and SDNR pod were in crashloopbackoff error due to FAILED TO GET CERTIFICATE from AAF. dev-sdnc-0 0/2 Init:Error 31 3h4m dev-sdnc-ansible-server-

#sdnc #sdnr

Ccsdk / SDNC team I will be on vacation this week, so am canceling our call for 6/2. I also need to cancel our call on 6/9 due to conflict with the June LFN DDF event. We’ll meet next on 6/16. Dan Sen

#ccsdk #sdnc

Hi Dan, This is with reference to the item discussed in SDN-C weekly call. As per the discussion, the interaction between SDN-R and CPS will be done using RESP APIs for the yang-model related operatio

#ccsdk #sdnc

Hi team My name is Ruslan. I'm a software engineer at Pantheon.tech, also participating in ONAP CPS project. Currently i'm checking the state/usage of CCSDK/SLI framework and I'd like to clarify a few

#sdnc #ccsdk

https://www.ejbca.org/ part of contrib Von: onap-discuss@... <onap-discuss@...> Im Auftrag von minsang.yoon@... Gesendet: Freitag, 16. April 2021 15:22 An: ale

#sdnc #guilin #oom #deployment

What is the ejbca pods? It comes with which component?

#sdnc #guilin #oom #deployment

I don't see the issue with actual helm charts in guilin. at least two successful deployments. Out of your error messges I would investigate further all potential components in the chain: certcervice,

#sdnc #guilin #oom #deployment

I am facing the exact same problem. I know there was no this issue before maintenance release. I still have helm chart before maintenance release so I could deploy SDNC successfully with old chart. Bu

#sdnc #guilin #oom #deployment

Hi All, While deploying ONAP guilin release using oom, SDNC pods are not coming up: onapit-sdnc-0 0/2 Init:Error 6 29m onapit-sdnc-ansible-server-668576f5b4-pf76j 0/1 Init:1/2 2 29m onapit-sdnc-db-0 1

#sdnc #guilin #oom #deployment

CDS team, In the Honolulu release build, the CDS py-executor node is no longer starting. I have created a Highest severity Jira for this issue: https://jira.onap.org/browse/CCSDK-3200 This is a BLOCKI

#ccsdk #sdnc