Running with gitlab-runner 13.12.0 (7a6612da)  on gitlab-runners-bigbang-gitlab-runner-gitlab-runner-7df565ccnfc6 RsVhcwun  feature flags: FF_GITLAB_REGISTRY_HELPER_IMAGE:true section_start:1624464420:resolve_secrets Resolving secrets section_end:1624464420:resolve_secrets section_start:1624464420: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 ... section_end:1624464420:prepare_executor section_start:1624464420:prepare_script Preparing environment Waiting for pod gitlab-runners/runner-rsvhcwun-project-2316-concurrent-02l25x to be running, status is Pending Running on runner-rsvhcwun-project-2316-concurrent-02l25x via gitlab-runners-bigbang-gitlab-runner-gitlab-runner-7df565ccnfc6... section_end:1624464424:prepare_script section_start:1624464424:get_sources Getting source from Git repository Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/RsVhcwun/0/platform-one/big-bang/apps/third-party/jira/.git/ Created fresh repository. Checking out f460342b as refs/merge-requests/12/head... Skipping Git submodules setup section_end:1624464425:get_sources section_start:1624464425: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 | |-- files | | |-- server.xml | | `-- server.xml.j2 | |-- templates | | |-- NOTES.txt | | |-- _helpers.tpl | | |-- bigbang | | | |-- destinationrule.yaml | | | `-- virtualservice.yaml | | |-- config-jvm.yaml | | |-- db-credentials.yaml | | |-- ingress.yaml | | |-- nfs-permission-fixer.yaml | | |-- server-configmap.yaml | | |-- server-j2-configmap.yaml | | |-- service.yaml | | |-- serviceaccount.yaml | | |-- shared-home-pv.yaml | | |-- shared-home-pvc.yaml | | |-- statefulset.yaml | | `-- test | | |-- test-application-status.yaml | | |-- test-database-connectivity.yaml | | `-- test-shared-home-permissions.yaml | `-- values.yaml |-- docs | |-- README.md | `-- keycloak.md `-- tests |-- cy-run.sh |-- cypress | `-- integration | `-- jira-health.spec.js |-- cypress.json |-- main-test-gateway.yaml `-- test-values.yml 9 directories, 34 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 - jira in the StatefulSet RELEASE-NAME-jira is missing livenessProbe WARN - jira in the StatefulSet RELEASE-NAME-jira does not have a memory requests set WARN - jira in the StatefulSet RELEASE-NAME-jira does not have a CPU requests set WARN - jira in the StatefulSet RELEASE-NAME-jira does not have a memory limit set WARN - jira in the StatefulSet RELEASE-NAME-jira does not have a CPU limit set WARN - jira in the StatefulSet RELEASE-NAME-jira does not have QoS class of Guaranteed WARN - jira in the StatefulSet RELEASE-NAME-jira has ability to run as root WARN - jira in the StatefulSet RELEASE-NAME-jira has a UID of less than 1000 WARN - StatefulSet RELEASE-NAME-jira using defaulting to image UID WARN - jira in the StatefulSet RELEASE-NAME-jira is not using a read only root filesystem WARN - test in the Pod RELEASE-NAME-jira-application-status-test is missing livenessProbe WARN - test in the Pod RELEASE-NAME-jira-application-status-test is missing readinessProbe WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have a memory requests set WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have a CPU requests set WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have a memory limit set WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have a CPU limit set WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have QoS class of Guaranteed WARN - Pod RELEASE-NAME-jira-application-status-test is using default Service Account WARN - test in the Pod RELEASE-NAME-jira-application-status-test has ability to run as root WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test is missing livenessProbe WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test is missing readinessProbe WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have a memory requests set WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have a CPU requests set WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have a memory limit set WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have a CPU limit set WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have QoS class of Guaranteed WARN - Pod RELEASE-NAME-jira-shared-home-permissions-test is using default Service Account WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test has ability to run as root WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test has a UID of less than 1000 WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test is not using a read only root filesystem 47 tests, 17 passed, 30 warnings, 0 failures Checking chart values... WARN - jira in the StatefulSet RELEASE-NAME-jira is not using a read only root filesystem WARN - jira in the StatefulSet RELEASE-NAME-jira does not have a memory requests set WARN - jira in the StatefulSet RELEASE-NAME-jira does not have a CPU requests set WARN - jira in the StatefulSet RELEASE-NAME-jira does not have a memory limit set WARN - jira in the StatefulSet RELEASE-NAME-jira does not have a CPU limit set WARN - jira in the StatefulSet RELEASE-NAME-jira does not have QoS class of Guaranteed WARN - jira in the StatefulSet RELEASE-NAME-jira has ability to run as root WARN - jira in the StatefulSet RELEASE-NAME-jira has a UID of less than 1000 WARN - StatefulSet RELEASE-NAME-jira using defaulting to image UID WARN - jira in the StatefulSet RELEASE-NAME-jira is missing livenessProbe WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have a memory requests set WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have a CPU requests set WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have a memory limit set WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have a CPU limit set WARN - test in the Pod RELEASE-NAME-jira-application-status-test does not have QoS class of Guaranteed WARN - Pod RELEASE-NAME-jira-application-status-test is using default Service Account WARN - test in the Pod RELEASE-NAME-jira-application-status-test has ability to run as root WARN - test in the Pod RELEASE-NAME-jira-application-status-test is missing livenessProbe WARN - test in the Pod RELEASE-NAME-jira-application-status-test is missing readinessProbe WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test is not using a read only root filesystem WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have a memory requests set WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have a CPU requests set WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have a memory limit set WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have a CPU limit set WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test does not have QoS class of Guaranteed WARN - Pod RELEASE-NAME-jira-shared-home-permissions-test is using default Service Account WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test has ability to run as root WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test has a UID of less than 1000 WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test is missing livenessProbe WARN - test in the Pod RELEASE-NAME-jira-shared-home-permissions-test is missing readinessProbe 43 tests, 13 passed, 30 warnings, 0 failures $ if [ -d "tests/policy" ]; then # collapsed multi-line command section_end:1624464425:step_script section_start:1624464425:cleanup_file_variables Cleaning up file based variables section_end:1624464426:cleanup_file_variables Job succeeded