Running with gitlab-runner 13.6.0 (8fa89735)  on bigbang-public-runner-gitlab-runner-848b4ffbcd-gxfzz pP4YiAQX section_start:1615393999:resolve_secrets Resolving secrets section_end:1615393999:resolve_secrets section_start:1615393999:prepare_executor Preparing the "kubernetes" executor Using Kubernetes namespace: private-bigbang-runner Using Kubernetes executor with image registry.dso.mil/platform-one/big-bang/pipeline-templates/pipeline-templates/k3d-builder:afdd9b77 ... section_end:1615393999:prepare_executor section_start:1615393999:prepare_script Preparing environment Waiting for pod private-bigbang-runner/runner-pp4yiaqx-project-4691-concurrent-0vzv8z to be running, status is Pending Waiting for pod private-bigbang-runner/runner-pp4yiaqx-project-4691-concurrent-0vzv8z to be running, status is Pending ContainersNotReady: "containers with unready status: [build helper svc-0]" ContainersNotReady: "containers with unready status: [build helper svc-0]" Running on runner-pp4yiaqx-project-4691-concurrent-0vzv8z via bigbang-public-runner-gitlab-runner-848b4ffbcd-gxfzz... section_end:1615394005:prepare_script section_start:1615394005:get_sources Getting source from Git repository Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/platform-one/big-bang/apps/sandbox/postgres-operator/.git/ Created fresh repository. Checking out 40357a77 as bb-16/BigBang-Addon... Skipping Git submodules setup section_end:1615394005:get_sources section_start:1615394005:step_script Executing "step_script" stage of the job script $ docker run -d -p 53:53/udp -p 53:53 registry.dso.mil/platform-one/big-bang/pipeline-templates/pipeline-templates/go-dnsmasq:87fca1d1 Unable to find image 'registry.dso.mil/platform-one/big-bang/pipeline-templates/pipeline-templates/go-dnsmasq:87fca1d1' locally 87fca1d1: Pulling from platform-one/big-bang/pipeline-templates/pipeline-templates/go-dnsmasq a6b97b4963f5: Pulling fs layer 13948a011eec: Pulling fs layer 420065a186b9: Pulling fs layer 3b4ee3c09e52: Pulling fs layer 13948a011eec: Verifying Checksum 13948a011eec: Download complete 420065a186b9: Download complete 3b4ee3c09e52: Verifying Checksum 3b4ee3c09e52: Download complete a6b97b4963f5: Verifying Checksum a6b97b4963f5: Download complete a6b97b4963f5: Pull complete 13948a011eec: Pull complete 420065a186b9: Pull complete 3b4ee3c09e52: Pull complete Digest: sha256:9d8416babf25e66a6a7e47a545b98a36e5d4fb8aeadf083ed5bd4d6e2b80e923 Status: Downloaded newer image for registry.dso.mil/platform-one/big-bang/pipeline-templates/pipeline-templates/go-dnsmasq:87fca1d1 199851e5c7db6d2f57ef48602a0305b2e1fa65d8de1ec1c2a153fd7593be1472 $ echo "nameserver 127.0.0.1" >> /etc/resolv.conf $ k3d cluster create ${CI_PROJECT_NAME} --servers 1 --k3s-server-arg "--disable=metrics-server" --k3s-server-arg "--disable=traefik" -p 80:80@loadbalancer -p 443:443@loadbalancer --wait INFO[0000] Created network 'k3d-postgres-operator' INFO[0000] Created volume 'k3d-postgres-operator-images' INFO[0001] Creating node 'k3d-postgres-operator-server-0' INFO[0002] Pulling image 'docker.io/rancher/k3s:v1.19.4-k3s1' INFO[0012] Creating LoadBalancer 'k3d-postgres-operator-serverlb' INFO[0013] Pulling image 'docker.io/rancher/k3d-proxy:v3.4.0' INFO[0017] (Optional) Trying to get IP of the docker host and inject it into the cluster as 'host.k3d.internal' for easy access INFO[0020] Successfully added host record to /etc/hosts in 2/2 nodes and to the CoreDNS ConfigMap INFO[0020] Cluster 'postgres-operator' created successfully! INFO[0020] You can now use it like this: kubectl cluster-info $ kubectl wait --for=condition=available --timeout 600s -A deployment --all > /dev/null $ kubectl wait --for=condition=ready --timeout 600s -A pods --all --field-selector status.phase=Running > /dev/null $ if [ ! -z ${PROJECT_NAME} ]; then # collapsed multi-line command namespace/postgres-operator created secret/private-registry created secret/private-registry-mil created $ git clone -b ${PIPELINE_REPO_BRANCH} ${PIPELINE_REPO} ${PIPELINE_REPO_DESTINATION} Cloning into '../pipeline-repo'... $ source ${YAML_PARSE_PATH} $ source ${WAIT_PATH} $ if [[ "${CI_PROJECT_NAME}" != *"istio"* ]]; then # collapsed multi-line command - Processing resources for Istio core. ✔ Istio core installed - Processing resources for Istiod. - Processing resources for Istiod. Waiting for Deployment/istio-system/istiod ✔ Istiod installed - Processing resources for Ingress gateways. - Processing resources for Ingress gateways. Waiting for Deployment/istio-system/istio-ingressgat... ✔ Ingress gateways installed - Pruning removed resources ✔ Installation complete$ if [ -f "tests/main-test-gateway.yaml" ]; then # collapsed multi-line command $ if [ -f "tests/dependencies.yaml" ]; then # collapsed multi-line command $ sleep 10 $ kubectl wait --for=condition=established --timeout 60s -A crd --all > /dev/null $ if [ -f ${dep_repo_folder}/tests/wait.sh ]; then # collapsed multi-line command $ wait_sts $ wait_daemonset $ kubectl wait --for=condition=available --timeout 600s -A deployment --all > /dev/null $ kubectl wait --for=condition=ready --timeout 600s -A pods --all --field-selector status.phase=Running > /dev/null $ if [ -f "tests/test-sysctl-mod.yml" ]; then # collapsed multi-line command $ echo "Package install" Package install $ if [ -f "tests/test-values.yml" ] ; then # collapsed multi-line command Helm installing postgres-operator/chart into postgres-operator namespace using postgres-operator/tests/test-values.yml for values manifest_sorter.go:192: info: skipping unknown hook: "crd-install" manifest_sorter.go:192: info: skipping unknown hook: "crd-install" manifest_sorter.go:192: info: skipping unknown hook: "crd-install" NAME: postgres-operator LAST DEPLOYED: Wed Mar 10 16:34:38 2021 NAMESPACE: postgres-operator STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: To verify that postgres-operator has started, run: kubectl --namespace=postgres-operator get pods -l "app.kubernetes.io/name=postgres-operator" $ sleep 10 $ kubectl wait --for=condition=established --timeout 60s -A crd --all > /dev/null $ if [ -f tests/wait.sh ]; then # collapsed multi-line command $ wait_sts $ wait_daemonset $ kubectl wait --for=condition=available --timeout 600s -A deployment --all > /dev/null $ kubectl wait --for=condition=ready --timeout 600s -A pods --all --field-selector status.phase=Running > /dev/null $ echo "Package tests" Package tests $ if [ $CI_PROJECT_NAME == "istio-system" ]; then # collapsed multi-line command $ if [ ! -z $(kubectl get services -n istio-system istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}') ] && [ ! -z $(kubectl get vs -A -o jsonpath='{.items[0].spec.hosts[0]}') ]; then # collapsed multi-line command error: error executing jsonpath "{.items[0].spec.hosts[0]}": Error executing template: array index out of bounds: index 0, length 0. Printing more information for debugging the template: template was: {.items[0].spec.hosts[0]} object given to jsonpath engine was: map[string]interface {}{"apiVersion":"v1", "items":[]interface {}{}, "kind":"List", "metadata":map[string]interface {}{"resourceVersion":"", "selfLink":""}} $ if [ -f "tests/cypress.json" ]; then # collapsed multi-line command $ touch $CI_PROJECT_DIR/success section_end:1615394097:step_script section_start:1615394097:after_script Running after_script Running after script... $ if [ -e success ]; then # collapsed multi-line command Job Succeeded $ k3d cluster delete ${CI_PROJECT_NAME} INFO[0000] Deleting cluster 'postgres-operator' INFO[0000] Deleted k3d-postgres-operator-serverlb INFO[0001] Deleted k3d-postgres-operator-server-0 INFO[0001] Deleting cluster network '613de0a7e893cb215577c6d320be7e0b5bf8fd5b1e2f35928da671e724d4e51b' INFO[0001] Deleting image volume 'k3d-postgres-operator-images' INFO[0001] Removing cluster details from default kubeconfig... INFO[0001] Removing standalone kubeconfig file (if there is one)... INFO[0001] Successfully deleted cluster postgres-operator! section_end:1615394099:after_script section_start:1615394099:upload_artifacts_on_success Uploading artifacts for successful job Uploading artifacts... WARNING: tests/cypress/screenshots: no matching files WARNING: tests/cypress/videos: no matching files  ERROR: No files to upload  section_end:1615394099:upload_artifacts_on_success section_start:1615394099:cleanup_file_variables Cleaning up file based variables section_end:1615394099:cleanup_file_variables Job succeeded