+ echo 'Starting step jenkins-smoke-tests.' Starting step jenkins-smoke-tests. + [[ -f /tmp/kubeconfig-2579368909 ]] + cp /tmp/kubeconfig-2579368909 /go/kubeconfig + export KUBECONFIG=/go/kubeconfig + KUBECONFIG=/go/kubeconfig + status=0 + oc version Client Version: 4.13.0-202307072116.p0.ge4c9a6a.assembly.stream-e4c9a6a Kustomize Version: v4.5.7 Server Version: 4.13.4 Kubernetes Version: v1.26.5+7d22122 + oc new-project test-jenkins Now using project "test-jenkins" on server "https://api.ci-rosa-h-a307.8ksf.s3.devshift.org:443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.43 -- /agnhost serve-hostname + make smoke Testing the jenkins template based install on openshift Collecting setuptools Downloading https://files.pythonhosted.org/packages/b0/3a/88b210db68e56854d0bcf4b38e165e03be377e13907746f825790f3df5bf/setuptools-59.6.0-py3-none-any.whl (952kB) Installing collected packages: setuptools Found existing installation: setuptools 39.2.0 Uninstalling setuptools-39.2.0: Successfully uninstalled setuptools-39.2.0 Successfully installed setuptools-59.6.0 You are using pip version 9.0.3, however version 23.1.2 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Collecting pip Downloading https://files.pythonhosted.org/packages/a4/6d/6463d49a933f547439d6b5b98b46af8742cc03ae83543e4d7688c2420f8b/pip-21.3.1-py3-none-any.whl (1.7MB) Installing collected packages: pip Found existing installation: pip 9.0.3 Uninstalling pip-9.0.3: Successfully uninstalled pip-9.0.3 Successfully installed pip-21.3.1 You are using pip version 21.3.1, however version 23.1.2 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Assigning value to variable TEST_NAMESPACE=test-jenkins Starting cleanup No resources found No resources found No resources found Logs directory created at /go/src/github.com/openshift/origin/out/logs/smoke Already on project "test-jenkins" on server "https://api.ci-rosa-h-a307.8ksf.s3.devshift.org:443". Starting Jenkins instance Running smoke tests in namespace with TEST_NAMESPACE=test-jenkins Logs will be collected in /go/src/github.com/openshift/origin/out/smoke Feature: Deploy Jenkins on openshift using template based install # smoke/features/jenkins-ephemeral.feature:1 As a user of openshift I want to deploy Jenkins and configure my CI/CD on openshift cluster Getting OC status before scenario [CODE] 0 [CMD] NAME DISPLAY NAME STATUS default Active ***Connected to cluster*** Background: # smoke/features/jenkins-ephemeral.feature:6 @automated @customer-scenario @interop Scenario: Create jenkins using ephemeral template : JKNS-02-TC01 # smoke/features/jenkins-ephemeral.feature:19 Given Project [TEST_NAMESPACE] is used # smoke/features/steps/steps.py:57 Given we have a openshift cluster # smoke/features/steps/login_steps.py:12 When User enters oc new-app jenkins-ephemeral command # smoke/features/steps/template_steps.py:12 Then we check that the resources are created # smoke/features/steps/build_steps.py:22 | resource | resource_name | | route | jenkins | | configmap | jenkins-trusted-ca-bundle | | deploymentconfig | jenkins | | serviceaccount | jenkins | | rolebinding | jenkins_edit | | service | jenkins-jnlp | | service | jenkins | Then We check for deployment pod status to be "Completed" # smoke/features/steps/build_steps.py:85 And We check for jenkins master pod status to be "Ready" # smoke/features/steps/steps.py:65 Feature: Delete all resources created using jenkins ephemeral template # smoke/features/jenkins-teardown-ephemeral.feature:1 We want to delete the resources created using jenkins ephemeral template We want this to continue in the same namespace & start testing the jenkins persistent template based install Getting OC status before scenario [CODE] 0 [CMD] NAME DISPLAY NAME STATUS default Active ***Connected to cluster*** Background: # smoke/features/jenkins-teardown-ephemeral.feature:6 @automated @customer-scenario @interop Scenario: Delete all resources : JKNS-05-TC01 # smoke/features/jenkins-teardown-ephemeral.feature:10 Given Project [TEST_NAMESPACE] is used # smoke/features/steps/steps.py:57 Given we have a openshift cluster # smoke/features/steps/login_steps.py:12 Then we delete deploymentconfig.apps.openshift.io "jenkins" # smoke/features/steps/delete_steps.py:7 And we delete route.route.openshift.io "jenkins" # smoke/features/steps/delete_steps.py:13 And delete configmap "jenkins-trusted-ca-bundle" # smoke/features/steps/delete_steps.py:19 And delete serviceaccount "jenkins" # smoke/features/steps/delete_steps.py:25 And delete rolebinding.authorization.openshift.io "jenkins_edit" # smoke/features/steps/delete_steps.py:31 And delete service "jenkins-jnlp" # smoke/features/steps/delete_steps.py:43 And delete service "jenkins" # smoke/features/steps/delete_steps.py:37 And delete all buildconfigs # smoke/features/steps/delete_steps.py:49 And delete all builds # smoke/features/steps/delete_steps.py:55 And delete all deploymentconfig # smoke/features/steps/delete_steps.py:61 And delete all services # smoke/features/steps/delete_steps.py:66 And delete all imagestream # smoke/features/steps/delete_steps.py:72 And delete all remaining test resources # smoke/features/steps/delete_steps.py:79 Feature: Deploy Jenkins with persistent volume on openshift using template based install # smoke/features/persistent-jenkins.feature:1 As a user of openshift I want to deploy Jenkins with persistent volume and configure my CI/CD on openshift cluster Getting OC status before scenario [CODE] 0 [CMD] NAME DISPLAY NAME STATUS default Active ***Connected to cluster*** Background: # smoke/features/persistent-jenkins.feature:6 @automated @customer-scenario @interop Scenario: Create jenkins using persistent template : JKNS-06-TC01 # smoke/features/persistent-jenkins.feature:10 Given Project [TEST_NAMESPACE] is used # smoke/features/steps/steps.py:57 Given we have a openshift cluster # smoke/features/steps/login_steps.py:12 When User enters oc new-app jenkins-persistent command # smoke/features/steps/template_steps.py:5 Then we check that the resources are created # smoke/features/steps/build_steps.py:22 | resource | resource_name | | route | jenkins | | configmap | jenkins-trusted-ca-bundle | | persistentvolumeclaim | jenkins | | deploymentconfig | jenkins | | serviceaccount | jenkins | | rolebinding | jenkins_edit | | service | jenkins-jnlp | | service | jenkins | Then we check the pvc status is "Bound" # smoke/features/steps/build_steps.py:89 Then We check for deployment pod status to be "Completed" # smoke/features/steps/build_steps.py:85 Traceback (most recent call last): File "/go/src/github.com/openshift/origin/out/venv3/lib64/python3.6/site-packages/behave/model.py", line 1329, in run match.run(runner.context) File "/go/src/github.com/openshift/origin/out/venv3/lib64/python3.6/site-packages/behave/matchers.py", line 98, in run self.func(context, *args, **kwargs) File "smoke/features/steps/build_steps.py", line 87, in deploymentPodStatus verify_status(context.current_project, 'pod', 'jenkins-1-deploy', poll_interval_seconds=2, max_retries=60, expected_status='Succeeded') File "smoke/features/steps/build_steps.py", line 105, in verify_status raise AssertionError AssertionError Captured stdout: TEST_NAMESPACE = test-jenkins Project test-jenkins is created!!! Using [test-jenkins] starting: --> Deploying template "test-jenkins/jenkins-persistent" to project test-jenkins Jenkins --------- Jenkins service, with persistent storage. NOTE: You must have persistent volumes available in your cluster to use this template. A Jenkins service has been created in your project. Log into Jenkins with your OpenShift account. The tutorial at https://github.com/openshift/origin/blob/master/examples/jenkins/README.md contains more information about using this template. * With parameters: * Jenkins Service Name=jenkins * Jenkins JNLP Service Name=jenkins-jnlp * Enable OAuth in Jenkins=true * Memory Limit=1Gi * Volume Capacity=1Gi * Jenkins ImageStream Namespace=openshift * Disable memory intensive administrative monitors=false * Allows control over how the JVM interacts with FIPS on startup.=-Dcom.redhat.fips=false * Jenkins ImageStreamTag=jenkins:2 * Fatal Error Log File=false * Allows use of Jenkins Update Center repository with invalid SSL certificate=false * Image used for the 'jnlp' container of the sample 'java-sidecar' and 'nodejs-sidecar' PodTemplates=image-registry.openshift-image-registry.svc:5000/openshift/jenkins-agent-base:latest * Image used for the 'java' container of the sample 'java-builder' PodTemplate=image-registry.openshift-image-registry.svc:5000/openshift/java:latest * Image used for the 'nodejs' container of the sample 'nodejs-builder' PodTemplate=image-registry.openshift-image-registry.svc:5000/openshift/nodejs:latest --> Creating resources ... route.route.openshift.io "jenkins" created configmap "jenkins-trusted-ca-bundle" created persistentvolumeclaim "jenkins" created deploymentconfig.apps.openshift.io "jenkins" created serviceaccount "jenkins" created rolebinding.authorization.openshift.io "jenkins_edit" created service "jenkins-jnlp" created service "jenkins" created --> Success Access your application via route 'jenkins-test-jenkins.apps.rosa.ci-rosa-h-a307.8ksf.s3.devshift.org' Run 'oc status' to view your app. , 0 Searching for route that matches jenkins in test-jenkins namespace Resource list is jenkins item matched jenkins Searching for configmap that matches jenkins-trusted-ca-bundle in test-jenkins namespace Resource list is jenkins-trusted-ca-bundle kube-root-ca.crt openshift-service-ca.crt item matched jenkins-trusted-ca-bundle Searching for persistentvolumeclaim that matches jenkins in test-jenkins namespace Resource list is jenkins item matched jenkins Searching for deploymentconfig that matches jenkins in test-jenkins namespace Resource list is jenkins item matched jenkins Searching for serviceaccount that matches jenkins in test-jenkins namespace Resource list is builder default deployer jenkins item matched jenkins Searching for rolebinding that matches jenkins_edit in test-jenkins namespace Resource list is admin jenkins_edit system:deployers system:image-builders system:image-pullers item matched jenkins_edit Searching for service that matches jenkins-jnlp in test-jenkins namespace Resource list is jenkins jenkins-jnlp item matched jenkins-jnlp Searching for service that matches jenkins in test-jenkins namespace Resource list is jenkins jenkins-jnlp item matched jenkins ---------Getting pvc status--------- Getting {object_type} status for {object_name} {object_type} {object_name} status:{status} Getting {object_type} status for {object_name} {object_type} {object_name} status:{status} And We check for jenkins master pod status to be "Ready" # None Feature: Upon jenkins master pod deletion/destruction the data(jobs) persist when using persistent template # smoke/features/persistent-test.feature:1 As a user of Jenkins persistent template I want to test upon jenkins master pod deletion/destruction the data(jobs) persist Getting OC status before scenario [CODE] 0 [CMD] NAME DISPLAY NAME STATUS default Active ***Connected to cluster*** Background: # smoke/features/persistent-test.feature:6 @automated @customer-scenario @interop Scenario: Test persistence of jenkins while using persistent template : JKNS-09-TC01 # smoke/features/persistent-test.feature:10 Given Project [TEST_NAMESPACE] is used # smoke/features/steps/steps.py:57 Given The jenkins pod is up and runnning # smoke/features/steps/steps.py:78 Traceback (most recent call last): File "/go/src/github.com/openshift/origin/out/venv3/lib64/python3.6/site-packages/behave/model.py", line 1329, in run match.run(runner.context) File "/go/src/github.com/openshift/origin/out/venv3/lib64/python3.6/site-packages/behave/matchers.py", line 98, in run self.func(context, *args, **kwargs) File "smoke/features/steps/steps.py", line 80, in checkJenkins jenkinsMasterPodStatus(context) File "smoke/features/steps/steps.py", line 75, in jenkinsMasterPodStatus raise AssertionError AssertionError Captured stdout: TEST_NAMESPACE = test-jenkins Project test-jenkins is created!!! ---------Getting default jenkins pod name--------- jenkins-1-jqw9n false Then We rsh into the master pod and check the jobs count # None When We delete the jenkins master pod # None Then We ensure that jenkins deployment config is ready # None And We rsh into the master pod & Compare if the data persist or is lost upon pod restart # None Failing scenarios: smoke/features/persistent-jenkins.feature:10 Create jenkins using persistent template : JKNS-06-TC01 smoke/features/persistent-test.feature:10 Test persistence of jenkins while using persistent template : JKNS-09-TC01 2 features passed, 2 failed, 0 skipped 2 scenarios passed, 2 failed, 0 skipped 27 steps passed, 2 failed, 5 skipped, 0 undefined Took 4m5.314s Logs collected in /go/src/github.com/openshift/origin/out/smoke + cp -r ./out /logs/artifacts/ + rename /TESTS- /junit_TESTS- /logs/artifacts/out/smoke/TESTS-jenkins-ephemeral.xml /logs/artifacts/out/smoke/TESTS-jenkins-teardown-ephemeral.xml /logs/artifacts/out/smoke/TESTS-persistent-jenkins.xml /logs/artifacts/out/smoke/TESTS-persistent-test.xml + echo 'Step jenkins-smoke-tests completed.' Step jenkins-smoke-tests completed. + exit 0