jx: jenkins X never came up on my kubernetes cluster on AWS

Summary

I kickstarted to use jenkinsX instead of using our standalone jenkins via kubernetes helm chart. I set the cluster and context and also added the bitbucket that we use for git repo.

jx install --provider aws --domain jenkins.<env_name>.<project_name>.<dns_name>.com --git-provider-url=‘https://bitbucket.org/<bitbucket_user>/jenkinsx’ --git-username=‘<bitbucket_user>’ --git-api-token=‘<bitbucket_user_token>’ --namespace=jenkins

Namespace jenkins created Using helmBinary helm with feature flag: none Context “<kubernetes_context_name>” modified. Storing the kubernetes provider aws in the TeamSettings Git configured for user: Samyak Rout and email srout@vlocity.com Using helm2 Configuring tiller Tiller Deployment is running in namespace kube-system existing ingress controller found, no need to install a new one Waiting for external loadbalancer to be created and update the nginx-ingress-controller service in kube-system namespace External loadbalancer created Waiting to find the external host name of the ingress controller Service in namespace kube-system with name jxing-nginx-ingress-controller About to insert/update DNS CNAME record into HostedZone /hostedzone/Z3LZPTYR5VY4QP with wildcard *.jenkins.<env_name>.<project_name>.<dns_name>.com pointing to a6ab6b35825a711e9b1ee028efbc6ab8-47ba891e82d6a967.elb.us-east-2.amazonaws.com Updated HostZone ID /hostedzone/Z3LZPTYR5VY4QP successfully nginx ingress controller installed and configured Lets set up a Git user name and API token to be able to perform CI/CD

? Do you wish to use samyakr as the local Git user for https://bitbucket.org/samyakr/jenkinsx server: Yes Select the CI/CD pipelines Git server and user ? Do you wish to use https://bitbucket.org/samyakr/jenkinsx as the pipelines Git server: Yes ? Do you wish to use samyakr as the pipelines Git user for https://bitbucket.org/samyakr/jenkinsx server: Yes Setting the pipelines Git server https://bitbucket.org/samyakr/jenkinsx and user name samyakr. Saving the Git authentication configurationCurrent configuration dir: /Users/samyakrout/.jx options.Flags.CloudEnvRepository: https://github.com/jenkins-x/cloud-environments options.Flags.LocalCloudEnvironment: false Cloning the Jenkins X cloud environments repo to /Users/samyakrout/.jx/cloud-environments ? A local Jenkins X cloud environments repository already exists, recreate with latest? Yes Current configuration dir: /Users/samyakrout/.jx options.Flags.CloudEnvRepository: https://github.com/jenkins-x/cloud-environments options.Flags.LocalCloudEnvironment: false Cloning the Jenkins X cloud environments repo to /Users/samyakrout/.jx/cloud-environments Enumerating objects: 8, done. Counting objects: 100% (8/8), done. Compressing objects: 100% (6/6), done. Total 1373 (delta 2), reused 6 (delta 2), pack-reused 1365 ? Select Jenkins installation type: Serverless Jenkins No default password set, generating a random one Generated helm values /Users/samyakrout/.jx/extraValues.yaml Creating Secret jx-install-config in namespace jenkins Installing Jenkins X platform helm chart from: /Users/samyakrout/.jx/cloud-environments/env-aws

Installing knative into namespace jenkins Updating Helm repository… Helm repository update done. Upgrading Chart ‘upgrade --namespace jenkins --install --force --timeout 6000 --set build.auth.git.username=<kubernetes_context_name>-admin --set build.auth.git.password=<bitbucket_user_token> --set --set tillerNamespace= knative-build jenkins-x/knative-build’

retrying after error:failed to run ‘helm upgrade --namespace jenkins --install --force --timeout 6000 --set build.auth.git.username=<kubernetes_context_name>-admin --set build.auth.git.password=<bitbucket_user_token> ***** --set tillerNamespace= knative-build jenkins-x/knative-build’ command in directory ‘’, output: ‘Release “knative-build” does not exist. Installing it now. Error: apiVersion “caching.internal.knative.dev/v1alpha1” in knative-build/templates/image-git-init.yaml is not available’

Updating Helm repository… Helm repository update done. Upgrading Chart ‘upgrade --namespace jenkins --install --force --timeout 6000 --set build.auth.git.username=<kubernetes_context_name>-admin --set build.auth.git.password=<bitbucket_user_token> --set --set tillerNamespace= knative-build jenkins-x/knative-build’ Waiting for tiller pod to be ready, service account name is tiller, namespace is jenkins, tiller namespace is kube-system Waiting for cluster role binding to be defined, named tiller-role-binding in namespace jenkins tiller cluster role defined: cluster-admin in namespace jenkins tiller pod running ? Pick workload build pack: Kubernetes Workloads: Automated CI+CD with GitOps Promotion Setting the team build pack to kubernetes-workloads repo: https://github.com/jenkins-x-buildpacks/jenkins-x-kubernetes.git ref: master Installing jx into namespace jenkins Installing jenkins-x-platform version: 0.0.3321 Adding values file /Users/samyakrout/.jx/cloud-environments/env-aws/myvalues.yaml Adding values file /Users/samyakrout/.jx/adminSecrets.yaml Adding values file /Users/samyakrout/.jx/extraValues.yaml Adding values file /Users/samyakrout/.jx/cloud-environments/env-aws/secrets.yaml Upgrading Chart ‘upgrade --namespace jenkins --install --timeout 6000 --version 0.0.3321 --values /Users/samyakrout/.jx/cloud-environments/env-aws/myvalues.yaml --values /Users/samyakrout/.jx/adminSecrets.yaml --values /Users/samyakrout/.jx/extraValues.yaml --values /Users/samyakrout/.jx/cloud-environments/env-aws/secrets.yaml jenkins-x jenkins-x/jenkins-x-platform’ error: installing the Jenkins X platform: failed to install/upgrade the jenkins-x platform chart: failed to run ‘helm upgrade --namespace jenkins --install --timeout 6000 --version 0.0.3321 --values /Users/samyakrout/.jx/cloud-environments/env-aws/myvalues.yaml --values /Users/samyakrout/.jx/adminSecrets.yaml --values /Users/samyakrout/.jx/extraValues.yaml --values /Users/samyakrout/.jx/cloud-environments/env-aws/secrets.yaml jenkins-x jenkins-x/jenkins-x-platform’ command in directory ‘/Users/samyakrout/.jx/cloud-environments/env-aws’, output: ‘Error: UPGRADE FAILED: “jenkins-x” has no deployed releases’

Steps to reproduce the behavior

I went through the pre checks:

brew tap jenkins-x/jx brew install jx https://jenkins-x.io/getting-started/install-on-cluster/

Expected behavior

I was expecting the jenkinsx will be spinned up under the new jenkins namespace but hat didnt worked and it failed.

When I started cleaning the resources as there were failed helm charts related to the jenkins-x it could not, and threw error as below: (⎈ |devops3-vlocity:jenkins)➜ env-aws helm delete --purge jenkins-x Error: jobs.batch “cleanup” already exists (⎈ |devops3-vlocity:jenkins)➜ env-aws helm delete --purge jenkins-x Error: timed out waiting for the condition

And this get stucked in it.

Actual behavior

Expecting all the steps to be working on my cluster and that I can access Jenkins using my custom dns name

Jx version

The output of jx version is:

jx version
NAME               VERSION
jx                 1.3.821
jenkins x platform 0.0.3321
Kubernetes cluster v1.10.11
kubectl            v1.8.4
helm client        v2.9.1+g20adb27
helm server        canary+unreleased+g7161095
git                git version 2.17.0
Operating System   Mac OS X 10.13.4 build 17E199

Jenkins type

• Classic Jenkins
• Serverless Jenkins I selected Serverless Jenkins

Kubernetes cluster

I used kube-spray and ansible to create the k8s cluster on AWS and my k8s version is (⎈ |devops3-vlocity:jenkins)➜ cloud-environments git:(master) kubectl version Client Version: version.Info{Major:“1”, Minor:“8”, GitVersion:“v1.8.4”, GitCommit:“9befc2b8928a9426501d3bf62f72849d5cbcd5a3”, GitTreeState:“clean”, BuildDate:“2017-11-20T05:28:34Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“darwin/amd64”} Server Version: version.Info{Major:“1”, Minor:“10”, GitVersion:“v1.10.11”, GitCommit:“637c7e288581ee40ab4ca210618a89a555b6e7e9”, GitTreeState:“clean”, BuildDate:“2018-11-26T14:25:46Z”, GoVersion:“go1.9.3”, Compiler:“gc”, Platform:“linux/amd64”}

Operating system / Environment

coreos is the server worker OS but running the jx command from the client that is my macOS