Welcome to the Linux Foundation Forum!

egmentation error when trying to run pipelineruns from Chapter 10

Posts: 4
edited April 2023 in LFS269 Class Forum

Hi everyone,

I'm working on Exercise 10, and I'm having trouble running some of the provided pipelineruns in the examples.
Specifically, I'm see a segmentation error in the logs of the pipelineruns after they finish.

  1. administrator@gitops-server:~/Documents/tekton-ci/base$ tkn pr logs -f result-ci
  2. panic: runtime error: invalid memory address or nil pointer dereference
  3. [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x184b988]
  4.  
  5. goroutine 64 [running]:
  6. github.com/tektoncd/cli/pkg/pipelinerun.(*Tracker).Monitor(0xc0007aa400, {0x3346968, 0x0, 0x0})
  7. /workspace/src/github.com/tektoncd/cli/pkg/pipelinerun/tracker.go:70 +0x1e8
  8. github.com/tektoncd/cli/pkg/log.(*Reader).readLivePipelineLogs.func1()
  9. /workspace/src/github.com/tektoncd/cli/pkg/log/pipeline_reader.go:54 +0x1ef
  10. created by github.com/tektoncd/cli/pkg/log.(*Reader).readLivePipelineLogs
  11. /workspace/src/github.com/tektoncd/cli/pkg/log/pipeline_reader.go:49 +0xd1

Here is some information about my system:

  1. administrator@gitops-server:~/Documents/tekton-ci/base$ uname -a
  2. Linux gitops-server 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  1. administrator@gitops-server:~/Documents/tekton-ci/base$ k version --short
  2. Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
  3. Client Version: v1.26.3
  4. Kustomize Version: v4.5.7
  5. Server Version: v1.26.1-gke.1500
  1. administrator@gitops-server:~/Documents/tekton-ci/base$ k config get-contexts
  2. CURRENT NAME CLUSTER AUTHINFO NAMESPACE
  3. dev kind-lfs269-cluster kind-lfs269-cluster
  4. * staging gke_lfd269_europe-central2-a_cluster-1 gke_lfd269_europe-central2-a_cluster-1
  1. administrator@gitops-server:~/Documents/tekton-ci/base$ tkn version
  2. Client version: 0.22.0
  3. Pipeline version: v0.46.0
  1. administrator@gitops-server:~/Documents/tekton-ci/base$ k get all -n tekton-pipelines
  2. NAME READY STATUS RESTARTS AGE
  3. pod/tekton-pipelines-controller-cc78c8d78-dxngd 1/1 Running 0 42m
  4. pod/tekton-pipelines-webhook-84cf694998-k9c2f 1/1 Running 0 42m
  5.  
  6. NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
  7. service/tekton-pipelines-controller ClusterIP 10.96.8.29 <none> 9090/TCP,8008/TCP,8080/TCP 42m
  8. service/tekton-pipelines-webhook ClusterIP 10.96.11.233 <none> 9090/TCP,8008/TCP,443/TCP,8080/TCP 42m
  9.  
  10. NAME READY UP-TO-DATE AVAILABLE AGE
  11. deployment.apps/tekton-pipelines-controller 1/1 1 1 42m
  12. deployment.apps/tekton-pipelines-webhook 1/1 1 1 42m
  13.  
  14. NAME DESIRED CURRENT READY AGE
  15. replicaset.apps/tekton-pipelines-controller-cc78c8d78 1 1 1 42m
  16. replicaset.apps/tekton-pipelines-webhook-84cf694998 1 1 1 42m
  17.  
  18. NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE
  19. horizontalpodautoscaler.autoscaling/tekton-pipelines-webhook Deployment/tekton-pipelines-webhook 3%/100% 1 5 1 42m
  1. administrator@gitops-server:~/Documents/tekton-ci/base$ tkn p describe instavote-ci
  2. Name: instavote-ci
  3. Namespace: default
  4. Description: This is a pipeline template which performs the follwing tasks:
  5. - Clones a subset of file for one microservice from a mono-repo
  6. e.g. vote/* result/* worker/* matching patterns provided.
  7. - Lists all the files from the cloned workspace to validate if
  8. it has cloned the correct subpath matching your microservice.
  9. - Builds a container image from the workspace which contains
  10. the Dockerfile. It accepts imageUrl and imageTag params to
  11. define the tag. The same task also pushes the image to the
  12. registry.
  13. Some of the additional notable features of this template include:
  14. - Cloned repo is passed to subsequent Tasks using a Workspace.
  15. - Orders Tasks in a Pipeline using "runAfter" so that
  16. git-clone completes before we try to read from the Workspace
  17. to find the Dockerfile and build an image.
  18. - Uses a volumeClaimTemplate Volume as a Workspace.
  19. - Uses a secret generated with config.json and mounts it
  20. as a worksapce with name dockerconfig to provide registry
  21. credentials.
  22. - Avoids hard-coded paths by using a Workspace's path
  23. variable instead.
  24.  
  25.  
  26. ⚓ Params
  27.  
  28. NAME TYPE DESCRIPTION DEFAULT VALUE
  29. ∙ repoUrl string The git repository ... ---
  30. ∙ revision string The git branch,tag,... ---
  31. ∙ sparseCheckoutDirectories string directory patterns ... ---
  32. ∙ imageUrl string URL of image reposi... user/repo
  33. ∙ imageTag string Tag to apply to the... latest
  34. ∙ pathToContext string The path to the bui... .
  35. ∙ pathToDockerFile string The path to the doc... Dockerfile
  36.  
  37. 📂 Workspaces
  38.  
  39. NAME DESCRIPTION
  40. ∙ shared-data This workspace will...
  41. ∙ dockerconfig Add docker's config...
  42.  
  43. 🗒 Tasks
  44.  
  45. NAME TASKREF RUNAFTER TIMEOUT CONDITIONS PARAMS
  46. ∙ fetch-repo git-clone --- --- url: string, revision: string, sparseCheckoutDirectories: string
  47. ∙ misc EMBEDDED fetch-repo --- --- commit-hash:
  48. ∙ img-build-publish kaniko misc --- --- CONTEXT: ., IMAGE: , EXTRA_ARGS: [ --skip-tls-verify ]
  49. ∙ verify-digest EMBEDDED img-build-publish --- --- digest:
  50.  
  51. ⛩ PipelineRuns
  52.  
  53. NAME STARTED DURATION STATUS
  54. ∙ result-ci 18 minutes ago 18 seconds Failed
  55. ∙ vote-ci 22 minutes ago 17 seconds Failed
  56.  
  1. administrator@gitops-server:~/Documents/tekton-ci/base$ k get storageclasses.storage.k8s.io
  2. NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
  3. premium-rwo pd.csi.storage.gke.io Delete WaitForFirstConsumer true 3d9h
  4. standard kubernetes.io/gce-pd Delete Immediate true 3d9h
  5. standard-rwo (default) pd.csi.storage.gke.io Delete WaitForFirstConsumer true 3d9h
  6.  

I'm not sure what's causing this error or how to fix it. Can anyone help me troubleshoot this issue?

Thanks in advance!

Comments

  • Posts: 1,264

    Hi @manniqui,

    The fact that you are having a panic and a SIGSEGV on Tekton is pretty bad. So, something is happening with the Tekton binary; it could be a bug (some a similar error on https://github.com/tektoncd/pipeline/issues/4297), or the associated software could be spoiled in some way.

    So I suggest to uninstall and reinstall Tekton and try again. If it fails, I'd say you can get a new VM and reinstall everything, including the OS and the cluster software.

    Regards,
    Luis.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training