Pipelines never marked as finished (neither failed / success) after lighthouse / jx upgrade #7444
Labels
area/gc
kind/bug
Issue is a bug
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
ready-for-review
Summary
We've upgraded our cluster to the latest version of JX, we have several jobs which run for 120+ minutes, but when they terminate the github status never changes (neither to failed or successful). When looking at the pods they still terminate, so that leads me to assume that the issue could be with containers that run for too long, or perhaps the return value was of certain format which didn't register into the jenkins-x-controllerbuild. I can see that the container exited with
exit value 0
and with status Completed / Terminated.Below I added the output of
get
anddescribe
of the pod, which shows that it was completed, but still doesn't update the github environment. When looking at thejenkins-x-controller
I also can't see any logs that show the completion of the pod, so it seems the controllerbuild is not able to be notified.Is there any known issue about this? Is there further information that could be provided to understand what may be causing this?
The output of
kubectl get pod <jx-pipeline-pod>
:The output of
kubectl get pod <jx-pipeline-pod>
:Jx version
The output of
jx version
is:Diagnostic information
The output of
jx diagnose version
is:Kubernetes cluster
Kubectl version
The output of
kubectl version --client
is:Operating system / Environment
Linux ubuntu 18.04
The text was updated successfully, but these errors were encountered: