Running with gitlab-runner 13.6.0 (8fa89735)  on bigbang-public-runner-gitlab-runner-848b4ffbcd-gxfzz pP4YiAQX section_start:1615316478:resolve_secrets Resolving secrets section_end:1615316478:resolve_secrets section_start:1615316478: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:1615316478:prepare_executor section_start:1615316478:prepare_script Preparing environment Waiting for pod private-bigbang-runner/runner-pp4yiaqx-project-3874-concurrent-0z92vd to be running, status is Pending Running on runner-pp4yiaqx-project-3874-concurrent-0z92vd via bigbang-public-runner-gitlab-runner-848b4ffbcd-gxfzz... section_end:1615316481:prepare_script section_start:1615316481: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/developer-tools/haproxy/.git/ Created fresh repository. Checking out 44906858 as main... Skipping Git submodules setup section_end:1615316482:get_sources section_start:1615316482: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 3b4ee3c09e52: Waiting 13948a011eec: Verifying Checksum 13948a011eec: Download complete 420065a186b9: Verifying Checksum 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 8c9a641a1e0a1ab506f65f6bb07484c94d8c748855a4e56dc99edc5c4921cce0 $ 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-haproxy' INFO[0000] Created volume 'k3d-haproxy-images' INFO[0001] Creating node 'k3d-haproxy-server-0' INFO[0002] Pulling image 'docker.io/rancher/k3s:v1.19.4-k3s1' INFO[0028] Creating LoadBalancer 'k3d-haproxy-serverlb' INFO[0029] Pulling image 'docker.io/rancher/k3d-proxy:v3.4.0' INFO[0041] (Optional) Trying to get IP of the docker host and inject it into the cluster as 'host.k3d.internal' for easy access INFO[0045] Successfully added host record to /etc/hosts in 2/2 nodes and to the CoreDNS ConfigMap INFO[0045] Cluster 'haproxy' created successfully! INFO[0045] 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/haproxy 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 Generating a RSA private key ................................................................................................................+++++ ...............................................................+++++ writing new private key to 'tls.key' ----- secret/wildcard-cert created gateway.networking.istio.io/main created $ 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 $ 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 haproxy/chart into haproxy namespace using haproxy/tests/test-values.yml for values NAME: haproxy LAST DEPLOYED: Tue Mar 9 19:03:13 2021 NAMESPACE: haproxy STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: HAProxy has been has been successfully installed. This Chart is used to run HAProxy as a regular application, as opposed to HAProxy Ingress Controller Chart. Controller image deployed is: "registry1.dso.mil/ironbank/opensource/haproxy/haproxy22:v2.2.2". Your HAProxy app is of a "Deployment" kind. Service ports mapped are: - name: http containerPort: 8080 protocol: TCP - name: https containerPort: 8443 protocol: TCP - name: stat containerPort: 10024 protocol: TCP To be able to bind to privileged ports as non-root, the following is required: securityContext: enabled: true runAsUser: 1000 runAsGroup: 1000 initContainers: - name: sysctl image: "busybox:musl" command: - /bin/sh - -c - sysctl -w net.ipv4.ip_unprivileged_port_start=0 securityContext: privileged: true Node IP can be found with: $ kubectl --namespace haproxy get nodes -o jsonpath="{.items[0].status.addresses[1].address}" For more examples and up to date documentation, please visit: * Helm chart documentation: https://github.com/haproxytech/helm-charts/tree/master/haproxy * HAProxy Alpine Docker container documentation: https://github.com/haproxytech/haproxy-docker-alpine * HAProxy documentation: https://www.haproxy.org/download/2.2/doc/configuration.txt $ 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 $ 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 $ if [ -f "tests/cypress.json" ]; then # collapsed multi-line command $ touch $CI_PROJECT_DIR/success section_end:1615316613:step_script section_start:1615316613: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 'haproxy' INFO[0000] Deleted k3d-haproxy-serverlb INFO[0001] Deleted k3d-haproxy-server-0 INFO[0001] Deleting cluster network '0bcc29505d043adcf373a0d959da73d98c51b970655b6729f33f9992b9ab296d' INFO[0001] Deleting image volume 'k3d-haproxy-images' INFO[0001] Removing cluster details from default kubeconfig... INFO[0001] Removing standalone kubeconfig file (if there is one)... INFO[0001] Successfully deleted cluster haproxy! section_end:1615316615:after_script section_start:1615316615: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:1615316615:upload_artifacts_on_success section_start:1615316615:cleanup_file_variables Cleaning up file based variables section_end:1615316615:cleanup_file_variables Job succeeded