Running with gitlab-runner 14.1.0 (8925d9a0)  on gitlab-runners-bigbang-gitlab-runner-gitlab-runner-5fc8b59wbbzp hQqhwDZb section_start:1630344336:resolve_secrets Resolving secrets section_end:1630344336:resolve_secrets section_start:1630344336: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:1630344336:prepare_executor section_start:1630344336:prepare_script Preparing environment Waiting for pod gitlab-runners/runner-hqqhwdzb-project-7074-concurrent-08q7zm to be running, status is Pending Running on runner-hqqhwdzb-project-7074-concurrent-08q7zm via gitlab-runners-bigbang-gitlab-runner-gitlab-runner-5fc8b59wbbzp... section_end:1630344343:prepare_script section_start:1630344343:get_sources Getting source from Git repository Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/hQqhwDZb/0/platform-one/big-bang/apps/sandbox/vault/.git/ Created fresh repository. Checking out 87fb66d1 as refs/merge-requests/6/head... Skipping Git submodules setup section_end:1630344345:get_sources section_start:1630344345:step_script Executing "step_script" stage of the job script $ 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'... $ echo "Directory structure of repository:" Directory structure of repository: $ tree . . |-- CHANGELOG.md |-- CODEOWNERS |-- CONTRIBUTING.md |-- README.md |-- chart | |-- Chart.yaml | |-- Kptfile | |-- templates | | |-- NOTES.txt | | |-- _helpers.tpl | | |-- csi-clusterrole.yaml | | |-- csi-clusterrolebinding.yaml | | |-- csi-daemonset.yaml | | |-- csi-serviceaccount.yaml | | |-- injector-certs-secret.yaml | | |-- injector-clusterrole.yaml | | |-- injector-clusterrolebinding.yaml | | |-- injector-deployment.yaml | | |-- injector-leader-endpoint.yaml | | |-- injector-mutating-webhook.yaml | | |-- injector-network-policy.yaml | | |-- injector-psp-role.yaml | | |-- injector-psp-rolebinding.yaml | | |-- injector-psp.yaml | | |-- injector-role.yaml | | |-- injector-rolebinding.yaml | | |-- injector-service.yaml | | |-- injector-serviceaccount.yaml | | |-- server-clusterrolebinding.yaml | | |-- server-config-configmap.yaml | | |-- server-discovery-role.yaml | | |-- server-discovery-rolebinding.yaml | | |-- server-disruptionbudget.yaml | | |-- server-ha-active-service.yaml | | |-- server-ha-standby-service.yaml | | |-- server-headless-service.yaml | | |-- server-ingress.yaml | | |-- server-network-policy.yaml | | |-- server-psp-role.yaml | | |-- server-psp-rolebinding.yaml | | |-- server-psp.yaml | | |-- server-route.yaml | | |-- server-service.yaml | | |-- server-serviceaccount.yaml | | |-- server-statefulset.yaml | | |-- ui-service.yaml | | `-- vault-auto-init-seal | | |-- configmap-for-vault-init | | |-- job-to-initialize | | |-- pv-claim | | `-- vault-vs.yaml | |-- tests | | |-- cypress | | | |-- cypress.json | | | `-- vault-health.spec.js | | `-- server-test.yaml | |-- values.openshift.yaml | `-- values.yaml `-- tests |-- main-test-gateway.yaml `-- test-values.yaml 6 directories, 55 files $ echo "Generic configuration validation tests:" Generic configuration validation tests: $ if [ $(ls -1 tests/test-values.y*ml 2>/dev/null | wc -l) -gt 0 ]; then # collapsed multi-line command Checking test values... WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector has ability to run as root WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector using defaulting to image UID WARN - Deployment RELEASE-NAME-vault-agent-injector has a UID of less than 1000 WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector is not using a read only root filesystem WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have a memory requests set WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have a CPU requests set WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have a memory limit set WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have a CPU limit set WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have QoS class of Guaranteed WARN - Deployment RELEASE-NAME-vault-agent-injector must include Kubernetes recommended labels: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels WARN - vault in the StatefulSet RELEASE-NAME-vault has ability to run as root WARN - vault in the StatefulSet RELEASE-NAME-vault using defaulting to image UID WARN - StatefulSet RELEASE-NAME-vault has a UID of less than 1000 WARN - vault in the StatefulSet RELEASE-NAME-vault is missing livenessProbe WARN - vault in the StatefulSet RELEASE-NAME-vault is not using a read only root filesystem WARN - vault in the StatefulSet RELEASE-NAME-vault does not have a memory requests set WARN - vault in the StatefulSet RELEASE-NAME-vault does not have a CPU requests set WARN - vault in the StatefulSet RELEASE-NAME-vault does not have a memory limit set WARN - vault in the StatefulSet RELEASE-NAME-vault does not have a CPU limit set WARN - vault in the StatefulSet RELEASE-NAME-vault does not have QoS class of Guaranteed 48 tests, 28 passed, 20 warnings, 0 failures Checking chart values... WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector has ability to run as root WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector using defaulting to image UID WARN - Deployment RELEASE-NAME-vault-agent-injector has a UID of less than 1000 WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector is not using a read only root filesystem WARN - Deployment RELEASE-NAME-vault-agent-injector must include Kubernetes recommended labels: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have a memory requests set WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have a CPU requests set WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have a memory limit set WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have a CPU limit set WARN - sidecar-injector in the Deployment RELEASE-NAME-vault-agent-injector does not have QoS class of Guaranteed WARN - vault in the StatefulSet RELEASE-NAME-vault has ability to run as root WARN - vault in the StatefulSet RELEASE-NAME-vault using defaulting to image UID WARN - StatefulSet RELEASE-NAME-vault has a UID of less than 1000 WARN - vault in the StatefulSet RELEASE-NAME-vault is not using a read only root filesystem WARN - vault in the StatefulSet RELEASE-NAME-vault is missing livenessProbe WARN - vault in the StatefulSet RELEASE-NAME-vault does not have a memory requests set WARN - vault in the StatefulSet RELEASE-NAME-vault does not have a CPU requests set WARN - vault in the StatefulSet RELEASE-NAME-vault does not have a memory limit set WARN - vault in the StatefulSet RELEASE-NAME-vault does not have a CPU limit set WARN - vault in the StatefulSet RELEASE-NAME-vault does not have QoS class of Guaranteed 48 tests, 28 passed, 20 warnings, 0 failures $ if [ -d "tests/policy" ]; then # collapsed multi-line command section_end:1630344346:step_script section_start:1630344346:cleanup_file_variables Cleaning up file based variables section_end:1630344346:cleanup_file_variables Job succeeded