Hi Xin Miao,
SDNC component was not installed by default for me. I installed it manually
by executing the following helm install command and it worked for me. Could
you please uninstall SDNC and re-install with the following command with
override value *--set global.cmpv2Enabled=false.*
# *helm install dev-sdnc /root/helm3-storage/sdnc-9.0.0.tgz --set
global.cmpv2Enabled=false --namespace onap --set global.masterPassword=onap*
root@aarna-node-09:~# kubectl get pods -n onap |grep sdnc
dev-sdnc-0 2/2 Running
0 9d
dev-sdnc-ansible-server-7df98d44f9-t4j7g 1/1 Running
0 9d
dev-sdnc-dbinit-job-v7zql 0/1 Completed
0 9d
dev-sdnc-dgbuilder-55c64f79f5-v9z8x 1/1 Running
0 9d
dev-sdnc-dmaap-listener-9bd45b7fd-8msr7 1/1 Running
0 9d
dev-sdnc-sdnrdb-init-job-wlhb4 0/1 Completed
0 9d
dev-sdnc-ueb-listener-84ddd79554-pxhh8 1/1 Running
0 9d
dev-sdnc-web-5c4478797c-t5thl 1/1 Running
0 9d
dev-so-sdnc-adapter-7f8f679f89-tnb8g 2/2 Running
0 10d
Warm Regards,
*Raghuram*
Technical Support Engineer - L3
M: +91 9663155155
*CRN Top 10 Coolest Edge Computing Startups of 2020
<https://www.crn.com/slide-shows/networking/the-10-coolest-edge-computing-startups-of-2020/2>*
On Fri, Dec 3, 2021 at 9:32 PM [email protected] <[email protected]>
wrote:
> Hi, Raghuram,
>
>
>
> Thank you for your updates.
>
>
>
> I also have the following issue with SDNC in I release:
>
>
>
> dev-sdnc-0
> 0/2
> Init:0/5 0 25h
>
> dev-sdnc-ansible-server-c45585d44-h7csc 0/1
> Init:1/2 148 25h
>
> dev-sdnc-dbinit-job-29j7h 0/1
> Completed 0 25h
>
> dev-sdnc-dgbuilder-588f67b7d6-qjpqp 1/1
> Running 0 25h
>
> dev-sdnc-dmaap-listener-5988995d54-wtg75 0/1
> Init:1/2 0 25h
>
> dev-sdnc-sdnrdb-init-job-4cdjr 0/1
> Completed 0 25h
>
> dev-sdnc-ueb-listener-7fb7b4784c-2d2m4 0/1
> Init:1/2 0 25h
>
> dev-sdnc-web-6ffdf95fb8-bptgg 0/1
> Init:2/3 148 25h
>
>
>
> Have you run into this?
>
>
>
> @Dan,
>
> At the very beginning, ejbca was done and I restarted the pod and it came
> up.
>
> I also have cert-manager installed in my cluster.
>
> Should I redeploy SDNC in the cluster?
>
> What else shall I do?
>
> I am doing Rancher deployment with 1 master and 2 VMs (quite big VMs from
> resource perspective).
>
>
>
> Thanks a lot!
>
> Thanks,
>
>
>
> *Xin Miao*
>
> *Solution Engineering*
>
> *Fujitsu Network Communication*
>
> *(W)972-479-2263 (M)469-268-5226*
>
> *2811 Telecom Drive*
>
> *Richardson, TX 75081, USA*
>
>
>
> *From:* Raghuram Gopalshetty [mailto:[email protected]]
> *Sent:* Thursday, December 2, 2021 11:59 PM
> *To:* Miao, Xin <[email protected]>
> *Cc:* [email protected]
> *Subject:* Re: [onap-discuss] ONAP Istanbul - #aaf - dev-aaf-sms-preload
> pod is crashing - Init:CreateContainerConfigError
>
>
>
> Hi Xin Miao,
>
>
>
> The AAF SMS issue is not resolved yet. I have tried the ONAP install with
> the master branch and Istanbul branch and the problem remains the same. I
> also, see the same problem with OOF pods that you have posted on another
> email thread with I release.
>
>
> Warm Regards,
>
> *Raghuram*
>
> Technical Support Engineer - L3
>
> M: +91 9663155155
>
>
>
> *CRN Top 10 Coolest Edge Computing Startups of 2020
> <https://www.crn.com/slide-shows/networking/the-10-coolest-edge-computing-startups-of-2020/2>*
>
>
>
>
>
> On Thu, Dec 2, 2021 at 9:17 PM [email protected] <[email protected]>
> wrote:
>
> Hi, Ragharum,
>
>
>
> Have you ever got your AAF issue resolved?
>
>
>
> *Xin Miao*
>
>
>
> *From:* [email protected] [mailto:[email protected]] *On
> Behalf Of *Raghuram Gopalshetty
> *Sent:* Thursday, November 25, 2021 10:11 AM
> *To:* [email protected]; [email protected]
> *Subject:* Re: [onap-discuss] ONAP Istanbul - #aaf - dev-aaf-sms-preload
> pod is crashing - Init:CreateContainerConfigError
>
>
>
> I have also attached the ONAP Istanbul Health Check result.
>
>
> Warm Regards,
>
> *Raghuram*
>
>
>
> *CRN Top 10 Coolest Edge Computing Startups of 2020
> <https://www.crn.com/slide-shows/networking/the-10-coolest-edge-computing-startups-of-2020/2>*
>
>
>
>
>
> On Thu, Nov 25, 2021 at 9:13 PM raghuramg via lists.onap.org <raghuramg=
> [email protected]> wrote:
>
> Hi Team,
>
> I am installing ONAP Istanbul and the following pod is crashing with the
> message: *Init:CreateContainerConfigError.* I have attached the pod
> describe output and list of pods from the ONAP namespace.
> Please advise on steps to fix this problem. Many Thanks.
>
> root@aarna-node-09:~# *kubectl get pods -n onap dev-aaf-sms-preload-bb4qx*
>
> NAME READY STATUS
> RESTARTS AGE
>
> dev-aaf-sms-preload-bb4qx 0/1 Init:CreateContainerConfigError 0
> 3h39m
>
> root@aarna-node-09:~# *kubectl logs -n onap dev-aaf-sms-preload-bb4qx*
>
> Error from server (BadRequest): container "aaf-sms-preload" in pod
> "dev-aaf-sms-preload-bb4qx" is waiting to start: PodInitializing
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#23682): https://lists.onap.org/g/onap-discuss/message/23682
Mute This Topic: https://lists.onap.org/mt/87304565/21656
Mute #aaf:https://lists.onap.org/g/onap-discuss/mutehashtag/aaf
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
