Running with gitlab-runner 14.1.0 (8925d9a0)  on gitlab-runners-bigbang-gl-packages-privileged-gitlab-runneb7dvc L_wAsvdS section_start:1630343778:resolve_secrets Resolving secrets section_end:1630343778:resolve_secrets section_start:1630343778:prepare_executor Preparing the "kubernetes" executor Using Kubernetes namespace: gitlab-runners Using Kubernetes executor with image registry.dso.mil/platform-one/big-bang/pipeline-templates/pipeline-templates/k3d-builder:0.0.5 ... Using attach strategy to execute scripts... section_end:1630343778:prepare_executor section_start:1630343778:prepare_script Preparing environment Waiting for pod gitlab-runners/runner-lwasvds-project-7074-concurrent-0mbk6v to be running, status is Pending Running on runner-lwasvds-project-7074-concurrent-0mbk6v via gitlab-runners-bigbang-gl-packages-privileged-gitlab-runneb7dvc... section_end:1630343785:prepare_script section_start:1630343785:get_sources Getting source from Git repository Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/L_wAsvdS/0/platform-one/big-bang/apps/sandbox/vault/.git/ Created fresh repository. Checking out 4df9c21a as refs/merge-requests/7/head... Skipping Git submodules setup section_end:1630343787:get_sources section_start:1630343787:step_script Executing "step_script" stage of the job script $ echo -e "\e[0Ksection_start:`date +%s`:cluster_setup[collapsed=true]\r\e[0KCluster Setup" section_start:1630343787:cluster_setup[collapsed=true] Cluster Setup $ if [ -z ${PIPELINE_REPO_BRANCH} ]; then # collapsed multi-line command $ git clone -b ${PIPELINE_REPO_BRANCH} ${PIPELINE_REPO} ${PIPELINE_REPO_DESTINATION} Cloning into '../pipeline-repo'... $ source ${WAIT_PATH} $ i=0; while [ "$i" -lt 12 ]; do docker info &>/dev/null && break; sleep 5; i=$(( i + 1 )) ; done $ docker network create ${CI_JOB_ID} --driver=bridge -o "com.docker.network.driver.mtu"="1450" 09c0bce145d71961111983d742a83a653ad6874cceff4afaf59380418491bc51 $ k3d cluster create ${CI_JOB_ID} --config ${K3D_CONFIG_PATH} --network ${CI_JOB_ID} INFO[0000] Using config file ../pipeline-repo/jobs/k3d-ci/config.yaml INFO[0000] Prep: Network INFO[0000] Network with name '6081867' already exists with ID '09c0bce145d71961111983d742a83a653ad6874cceff4afaf59380418491bc51' INFO[0000] Created volume 'k3d-6081867-images' INFO[0001] Creating node 'k3d-6081867-server-0' INFO[0002] Pulling image 'docker.io/rancher/k3s:v1.20.4-k3s1' INFO[0004] Creating LoadBalancer 'k3d-6081867-serverlb' INFO[0005] Pulling image 'docker.io/rancher/k3d-proxy:v4.3.0' INFO[0007] Starting cluster '6081867' INFO[0007] Starting servers... INFO[0007] Starting Node 'k3d-6081867-server-0' INFO[0012] Starting agents... INFO[0012] Starting helpers... INFO[0012] Starting Node 'k3d-6081867-serverlb' INFO[0013] (Optional) Trying to get IP of the docker host and inject it into the cluster as 'host.k3d.internal' for easy access INFO[0016] Successfully added host record to /etc/hosts in 2/2 nodes and to the CoreDNS ConfigMap INFO[0016] Cluster '6081867' created successfully! INFO[0016] --kubeconfig-update-default=false --> sets --kubeconfig-switch-context=false INFO[0016] You can now use it like this: kubectl config use-context k3d-6081867 kubectl cluster-info $ until kubectl get deployment coredns -n kube-system -o go-template='{{.status.availableReplicas}}' | grep -v -e ''; do sleep 1s; done 1 $ if [ ! -z ${PROJECT_NAME} ]; then # collapsed multi-line command namespace/vault created secret/private-registry created secret/private-registry-mil created $ echo -e "\e[0Ksection_end:`date +%s`:cluster_setup\r\e[0K" section_end:1630343823:cluster_setup  $ echo -e "\e[0Ksection_start:`date +%s`:dependency_clean[collapsed=true]\r\e[0KDependency Install and Wait" section_start:1630343823:dependency_clean[collapsed=true] Dependency Install and Wait $ if [ -f "tests/dependencies.yaml" ]; then # collapsed multi-line command $ if [ -f "tests/dependencies.yaml" ]; then # collapsed multi-line command $ echo -e "\e[0Ksection_end:`date +%s`:dependency_clean\r\e[0K" section_end:1630343823:dependency_clean  $ if [ ! -z ${PROJECT_NAME} ]; then # collapsed multi-line command Helm installing vault/chart into vault namespace using vault/tests/test-values.yaml for values Release "vault" does not exist. Installing it now. NAME: vault LAST DEPLOYED: Mon Aug 30 17:17:03 2021 NAMESPACE: vault STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: Thank you for installing HashiCorp Vault! Now that you have deployed Vault, you should look over the docs on using Vault with Kubernetes available here: https://www.vaultproject.io/docs/ Your release is named vault. To learn more about the release, try: $ helm status vault $ helm get manifest vault $ sleep 10 # collapsed multi-line command $ if [ -d "chart/templates/tests" ]; then # collapsed multi-line command $ touch $CI_PROJECT_DIR/success $ echo -e "\e[0Ksection_start:`date +%s`:image_fetch[collapsed=true]\r\e[0KFetch Images" section_start:1630343871:image_fetch[collapsed=true] Fetch Images $ images=$(timeout 65 bash -c "until docker exec -i k3d-${CI_JOB_ID}-server-0 crictl images -o json; do sleep 10; done;") $ echo $images | jq -r '.images[].repoTags[0] | select(. != null)' | tee images.txt docker.io/rancher/coredns-coredns:1.8.0 docker.io/rancher/library-busybox:1.32.1 docker.io/rancher/local-path-provisioner:v0.0.19 docker.io/rancher/metrics-server:v0.3.6 docker.io/rancher/pause:3.1 registry1.dso.mil/ironbank/hashicorp/vault/vault-k8s:0.11.0 registry1.dso.mil/ironbank/hashicorp/vault/vault:1.7.3 $ sed -i '/docker.io\/rancher\//d' images.txt $ if [ -f tests/images.txt ]; then # collapsed multi-line command $ echo -e "\e[0Ksection_end:`date +%s`:image_fetch\r\e[0K" section_end:1630343872:image_fetch  section_end:1630343872:step_script section_start:1630343872:after_script Running after_script Running after script... $ if [ -e success ]; then # collapsed multi-line command section_start:1630343872:cluster_status[collapsed=true] Cluster Status Job Succeeded, cluster status: NAMESPACE NAME READY STATUS RESTARTS AGE kube-system pod/local-path-provisioner-5ff76fc89d-cm7pz 1/1 Running 0 59s kube-system pod/metrics-server-86cbb8457f-q6nt8 1/1 Running 0 59s kube-system pod/coredns-854c77959c-gphmb 1/1 Running 0 59s vault pod/vault-agent-injector-7df895cfd4-bkp96 1/1 Running 0 49s vault pod/vault-job-init-hg7zl 0/1 Completed 0 46s vault pod/vault-0 1/1 Running 0 48s NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE default service/kubernetes ClusterIP 10.43.0.1 443/TCP 73s kube-system service/kube-dns ClusterIP 10.43.0.10 53/UDP,53/TCP,9153/TCP 71s kube-system service/metrics-server ClusterIP 10.43.164.245 443/TCP 71s vault service/vault-internal ClusterIP None 8200/TCP,8201/TCP 49s vault service/vault ClusterIP 10.43.239.90 8200/TCP,8201/TCP 49s vault service/vault-agent-injector-svc ClusterIP 10.43.233.128 443/TCP 49s NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE kube-system deployment.apps/local-path-provisioner 1/1 1 1 71s kube-system deployment.apps/metrics-server 1/1 1 1 71s kube-system deployment.apps/coredns 1/1 1 1 71s vault deployment.apps/vault-agent-injector 1/1 1 1 49s NAMESPACE NAME DESIRED CURRENT READY AGE kube-system replicaset.apps/local-path-provisioner-5ff76fc89d 1 1 1 59s kube-system replicaset.apps/metrics-server-86cbb8457f 1 1 1 59s kube-system replicaset.apps/coredns-854c77959c 1 1 1 59s vault replicaset.apps/vault-agent-injector-7df895cfd4 1 1 1 49s NAMESPACE NAME READY AGE vault statefulset.apps/vault 1/1 49s NAMESPACE NAME COMPLETIONS DURATION AGE vault job.batch/vault-job-init 1/1 39s 49s section_end:1630343872:cluster_status  $ echo -e "\e[0Ksection_start:`date +%s`:cluster_clean[collapsed=true]\r\e[0KCluster Cleanup" section_start:1630343872:cluster_clean[collapsed=true] Cluster Cleanup $ k3d cluster delete ${CI_JOB_ID} INFO[0000] Deleting cluster '6081867' INFO[0000] Deleted k3d-6081867-serverlb INFO[0001] Deleted k3d-6081867-server-0 INFO[0001] Deleting image volume 'k3d-6081867-images' INFO[0001] Removing cluster details from default kubeconfig... INFO[0001] Removing standalone kubeconfig file (if there is one)... INFO[0001] Successfully deleted cluster 6081867! $ docker network rm ${CI_JOB_ID} 6081867 $ echo -e "\e[0Ksection_end:`date +%s`:cluster_clean\r\e[0K" section_end:1630343874:cluster_clean  section_end:1630343874:after_script section_start:1630343874:upload_artifacts_on_success Uploading artifacts for successful job Uploading artifacts... images.txt: found 1 matching files and directories WARNING: tests/cypress/screenshots: no matching files WARNING: tests/cypress/videos: no matching files  WARNING: cypress-artifacts: no matching files  Uploading artifacts as "archive" to coordinator... ok id=6081867 responseStatus=201 Created token=djVimgza section_end:1630343875:upload_artifacts_on_success section_start:1630343875:cleanup_file_variables Cleaning up file based variables section_end:1630343875:cleanup_file_variables Job succeeded