It looks like a bug that was recently introduced in aai-resources. There is already a fix thanks to Alexis in oom: https://gerrit.onap.org/r/#/c/25955/, done on 9/Dec. Please use latest oom release-1.1.0
Regarding SDC, from the screenshot it looks like it takes long time pulling the image (it is quite large...) Hopefully until now it got solved. Anyway, if you encountered a problem to access sdc (503), you should recreate sdc pods (just delete them, helm will create them for you: sdc-cs, sdc-be, sdc-fe in this order). Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Potter, Nathaniel [mailto:[email protected]] Sent: Tuesday, December 12, 2017 8:29 PM To: Borislav Glozman <[email protected]>; Pavithra R13 <[email protected]>; [email protected] Subject: RE: [onap-discuss] [oom] Issue in ONAP Amsterdam release installation Hi all, I've seen some of these errors somewhat sporadically, but sometimes when I tear down and redeploy making no changes they'll come up correctly. The failure that I see in the pod is usually a sync error, like the following error in the aai-service pod that leads to the readiness container erroring out and the pod getting stuck in an init state: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 29m default-scheduler Successfully assigned aai-service-749944520-5dks6 to otconap3.sc.intel.com Normal SuccessfulMountVolume 29m kubelet, otconap3.sc.intel.com MountVolume.SetUp succeeded for volume "localtime" Normal SuccessfulMountVolume 29m kubelet, otconap3.sc.intel.com MountVolume.SetUp succeeded for volume "haproxy-cfg" Normal SuccessfulMountVolume 29m kubelet, otconap3.sc.intel.com MountVolume.SetUp succeeded for volume "aai-service-log" Normal SuccessfulMountVolume 29m kubelet, otconap3.sc.intel.com MountVolume.SetUp succeeded for volume "default-token-60hch" Normal Pulling 9m (x2 over 27m) kubelet, otconap3.sc.intel.com pulling image "oomk8s/readiness-check:1.0.0" Normal Pulled 9m (x2 over 20m) kubelet, otconap3.sc.intel.com Successfully pulled image "oomk8s/readiness-check:1.0.0" Normal Created 9m (x2 over 20m) kubelet, otconap3.sc.intel.com Created container Normal Started 9m (x2 over 20m) kubelet, otconap3.sc.intel.com Started container Warning FailedSync 9m kubelet, otconap3.sc.intel.com Error syncing pod In this same deployment my sdc-fe pod is getting the same sync error, is that the same warning you're seeing? Here's the final output of 'kubectl get pods --all-namespaces -a -o wide' in my setup. https://hastebin.com/mototaqihe.nginx Thanks, Nate Potter From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Borislav Glozman Sent: Tuesday, December 12, 2017 3:13 AM To: Pavithra R13 <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] [oom] Issue in ONAP Amsterdam release installation Please kindly send logs. The DNS warning is normal when using rancher 1.6.10, please ignore it. There may be some other error. Have you deployed config? Please provide output of 'kubectl get pods --all-namespaces -a -o wide' Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Pavithra R13 [mailto:[email protected]] Sent: Tuesday, December 12, 2017 4:08 AM To: [email protected]<mailto:[email protected]>; Borislav Glozman <[email protected]<mailto:[email protected]>> Subject: RE: [oom] [onap-discuss] Issue in ONAP Amsterdam release installation Hi We downloaded the latest oom and were able to proceed but now the fe and be of SDC , vnc portal and dmaap, global Kafka of message router are not coming up due to error "search line limits were exceeded. Some dns names were omitted". We have Internet access without any firewall and we have configured google dns in resolv.conf . So kindly help us in resolving this issue . Regards Pavithra ________________________________ From: Borislav Glozman <[email protected]<mailto:[email protected]>> Date: 11 December 2017 at 5:54:01 PM IST To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, Pavithra R13 <[email protected]<mailto:[email protected]>> Subject: RE: [onap-discuss] Issue in ONAP Amsterdam release installation Hi, Please add [oom] in subject. These workings you mentioned are not important and can be ignored. They are related to some Rancher bug that is supposed to be fixed. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Pavithra R13 Sent: Monday, December 11, 2017 1:38 PM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] Issue in ONAP Amsterdam release installation Hi All While trying to install ONAP Amsterdam release we are facing issue in bringing up message router(dmaap, global-kafka), vnc portal and sdc(be, fe) containers. The error is "searchline limits were exceeded, some dns names have been omitted." We have prepulled 1.1.10 branch and using v1.6.10 of rancher and 2.3 version of helm. We have set nameserver as 8.8.8.8 in /etc/resolv.conf. Please find attached screen shot of error and kindly help us in resolving the issue. Thanks & Regards, Pavithra R This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
