Troubleshooting on JayeX - Cloud Native CI/CD Built On Kubernetes

Install

Mon, 01 Jan 0001 00:00:00 +0000

Check you are using a cluster Git URL

If using Terraform make sure the values.auto.tfvars file contains a jx_git_url = value that points to a cluster git repo that contains a helmfile.yaml and a folder ./helmfiles. A common mistake is users set the jx_git_url to the infrastructure repo instead.

After a successful bootjob, these are few things to look for:

Secrets have been generated in the secret backend.
A webhook has been created in the cluster git repo.

Issues with secret generation

In some cases, the webhook generation will fail with a message :

jx gitops webhook update --warn-on-fail
Error: failed to find hmac token from secret:

This is normally because the secret generation failed during the boot job.

Bot Token

Mon, 01 Jan 0001 00:00:00 +0000

Commons problems with Bot Tokens

Make sure the bot user has access to the organisation and / or git repositories that it needs.

tip you can accept an organisation and repo GitHub invitation using

jx admin invitation

Make sure the bot token has the correct permissions to perform the action you require

Secrets

Mon, 01 Jan 0001 00:00:00 +0000

Commons problems with Secrets

Things to check:

the general health

jx health status -A

the boot job

jx admin logs

and make sure in the logs jx secret populate command is successful.

check the external secrets deployment and logs

kubectl get pods -n secret-infra
kubectl logs deploy/kubernetes-external-secrets -n secret-infra

check the status of the external secret using kubectl

kubectl get es -n [the namespace the secret / external secret is in]

Webhooks

Mon, 01 Jan 0001 00:00:00 +0000

Webhooks are used to trigger lighthouse when you:

merge commits to your main branch
open a Pull Request
push code to a Pull Request branch
comment on a Pull Request to trigger ChatOps

If webhooks are not working in your cluster then you won’t get ChatOps or pipelines triggered.

Requirements

For webhooks to work you must have a working Ingress for the hook endpoint from lighthouse

The ingress defaults to using the domain name specified in ingress.domain in your jx-requirements.yml file.

Quickstart/Import

Mon, 01 Jan 0001 00:00:00 +0000

After a successful installation of JayeX, the first thing to do is to either create a quickstart or import an existing repository into JayeX. They are both very similar, so the steps mentioned here can be applied for both.

Import/Quickstart involves the following steps:

Cloning of the dev/cluster git repository
Selecting and copying catalog folder into imported repository
Pull Request in the cluster git repository
Webhook creation in the imported repository
Addition of the repository name to the config configmap
Source repository creation in the jx namespace

Issues with cloning dev repository

If you encounter an issue of this form: