Modify the updateQueryData job to keep waiting

until the haproxy can be reached by
the kubernetes pod created by the job
For some reason in certain rare cases
the job is being started prematurely before
haproxy container is up so doing another check

Issue-ID: AAI-1713
Change-Id: I86827af46220eeb94322973d22a3abd4287eacea
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>

diff --git a/kubernetes/aai/charts/aai-traversal/templates/job.yaml b/kubernetes/aai/charts/aai-traversal/templates/job.yaml
index a018ede..599bbc2 100644 (file)
--- a/kubernetes/aai/charts/aai-traversal/templates/job.yaml
+++ b/kubernetes/aai/charts/aai-traversal/templates/job.yaml
@@ -58,6 +58,7 @@ spec:
         - |
           set -x
           mkdir -p /opt/aai/logroot/AAI-GQ/misc
+          until nc -w10 -z -v aai.{{.Release.Namespace}} 8443; do echo "Retrying to reach aai on port 8443"; done;
           bash -x /opt/app/aai-traversal/docker-entrypoint.sh install/updateQueryData.sh
         env:
         - name: LOCAL_USER_ID