Hi Tomasz, Sorry I don’t know the details of what the config-backend job is doing.
Note that the SDC team has changed their internal architecture and have introduced new containers (splitting the sdc-be container) so things will change again once we complete the new Helm charts. Cheers, Roger From: Tomasz Kapałka <tomasz.kapa...@amartus.com> Date: Tuesday, April 24, 2018 at 9:49 AM To: Roger Maitland <roger.maitl...@amdocs.com>, "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP code Hi Roger Thanks will check this. Could you please let mw know what exactly the config-backend pod is doing? As I have reviewed it and it seems that is only to make sure that sdc-be pod is running correctly. Am I right? BR Tomasz Kapalka From: Roger Maitland <roger.maitl...@amdocs.com> Sent: wtorek, 24 kwietnia 2018 15:28 To: Tomasz Kapałka <tomasz.kapa...@amartus.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP code Hi Tomasz, There is a known problem with how SDC starts up that may cause this problem. I suspect it’s due to a timing problem during startup (the readiness probes aren’t waiting long enough for the dev-sdc-be-config-backend job to complete). If you’d like to try to solve the problem, try changing the readiness ‘initialDelaySeconds’ values from 10 seconds to 30 seconds within sdc (if you grep you’ll see there are several of them). Thanks, Roger From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Tomasz Kapałka <tomasz.kapa...@amartus.com<mailto:tomasz.kapa...@amartus.com>> Date: Friday, April 20, 2018 at 12:03 PM To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP code Hi We are trying to start ONAP on GoogleCloud VM/Rancher/Kubernetes. We are using cd.sh script provided in https://jira.onap.org/browse/OOM-716 (the latest version: [^cd.sh).] The problem is with SDC-BE pod. It is shown in Kubernetes that it's working fine as port 8443 is open but when we try to get this port or 8080 via http we got 503 Service Unavailable. Few other pods like dev-sdc-be-config-backend, dev-sdc-fe are waiting for this service to respond properly but it's not doing that. We have reviewed the logs from sdc-be and there is nothing interesting at list from ERROR point of few. Seems that the service is not able to respond properly. Seems that the rest pods are waiting for sdc-be to create web context /sdc2 but this is not happening! Logs from SDC-BE: https://jira.onap.org/secure/attachment/11445/sdc-be.txt POD declaration: https://jira.onap.org/secure/attachment/11447/sdc-be-pod-configuration.yaml Could you please help? BR Tomasz Kapałka [stopka] Tomasz Kapałka Test Automation Programmer | Amartus www.amartus.com<http://www.amartus.com> HQ: 4/5 Burton Hall Park Sandyford Industrial Estate Dublin 18 Ireland | t: +353 1 663 80 00 R&D: ul. Wasilewskiego 20/14 30-305 Kraków Poland | t: +48 12 222 00 18 [cid:image002.png@01D3D890.66BBA4A0]<http://www.linkedin.com/company/amartus> [cid:image003.png@01D3D890.66BBA4A0] <https://twitter.com/amartus_com> [cid:image004.png@01D3D890.66BBA4A0] <https://plus.google.com/u/0/b/100551356470316259463/+amartus_sds> 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 onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
