Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job crashing with an error about finding a container in namespace "concourse" #8883

Open
sebastienbonami opened this issue Jan 9, 2024 · 1 comment
Labels

Comments

@sebastienbonami
Copy link

Summary

Hi, I have a job in a Concourse pipeline that result often (but not always) in an error like this:
wait for process completion: backend error: Exit status: 500, message: {"Type":"","Message":"get container: container \"e91b65f1-a04a-4bda-49ba-058520a956dc\" in namespace \"concourse\": not found","Handle":"","ProcessID":"","Binary":""}

The task that fails in the job is this one here: https://github.com/Ferlab-Ste-Justine/clin-prescription-ui/blob/2fce0427177eed8f72198e361c2830c7eec2f61c/ci/template.yml#L69-L75

My Concourse setup is in Kubernetes using this Helm chart: https://github.com/concourse/concourse-chart

I'm wondering what container Concourse is trying to find. The namespace concourse doesn't even actually exist in my Kubernetes cluster. The targetNamespace in my HelmRelease is not concourse so all Concourse resources like worker pods are in a namespace that is not named concourse.

Thanks for your help.

Triaging info

  • Concourse version: v7.11.0
  • Helm chart version: v17.2.1
@marco-m
Copy link
Contributor

marco-m commented Jan 11, 2024

Hello,
resource docker-image (what the pipeline you pointed to is using) is deprecated (see #6586).

I suggest to follow https://concourse-ci.org/building-and-pushing-an-image.html for the two-step replacement.

(This might or not definitely fix your problem, but is one less variable to thing about).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants