linode/apl-core

Tekton otomi pipeline does not start on initial deployment

j-zimnowoda opened this issue · 2 comments

j-zimnowoda commented

Describe the bug: (a clear and concise description of what the bug is)

To Reproduce
Steps to reproduce the behavior:

  1. Create GKE cluster
  2. Observe that Gitea webhook does not succeed

image.png

  1. Delete el-otomi-tekton-listener-674c845987-tg47q otomi-pipelines namespace
  2. Make a change in the values again.
  3. Observe that pipeline has been triggered

Expected behavior: (a clear and concise description of what you expected to happen)
Webhook always reach the Tekton pipeline listener

merll commented

Response to Gitea is

Delivery: Post "http://el-otomi-tekton-listener.otomi-pipelines.svc.cluster.local:8080": dial tcp: lookup el-otomi-tekton-listener.otomi-pipelines.svc.cluster.local: no such host

Deleting the service recreates it and assigns a different ClusterIP. Is there maybe a restriction in GKE we need to be aware of?

merll commented

During my tests last week I also noticed that repeated attempts to call the trigger, even without deleting the listener or the service, will eventually succeed when hitting "Test delivery" in Gitea. Unfortunately, there is probably no easy way to implement a retry here.