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

Builder pod that hit timeout is not terminated #4241

Closed
christophd opened this issue Apr 11, 2023 · 1 comment · Fixed by #4250
Closed

Builder pod that hit timeout is not terminated #4241

christophd opened this issue Apr 11, 2023 · 1 comment · Fixed by #4250
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@christophd
Copy link
Contributor

This is on Camel K 2.0

Since 2.0 the default build strategy is pod where each build is run via a builder pod. In case this build hits a timetout the Camel K operator tries to send a SIGTERM signal to the builder pod in order to terminate the build. Since 2.0 this mechanism is not working anymore (see error message below) and the pod and its build keeps running forever and all other builds get queued.

{"level":"info","ts":1680786033.9650033,"logger":"camel-k.controller.build","msg":"Invoking action monitor-pod","request-namespace":"camel-system","request-name":"kit-cgn8vko2ed2c73evf6h0","api-version":"camel.apache.org/v1","kind":"Build","ns":"camel-system","name":"kit-cgn8vko2ed2c73evf6h0"}
OCI runtime exec failed: exec failed: unable to start container process: exec: "kill": executable file not found in $PATH: unknown
{"level":"error","ts":1680786034.009642,"msg":"Reconciler error","controller":"build-controller","controllerGroup":"camel.apache.org","controllerKind":"Build","Build":{"name":"kit-cgn8vko2ed2c73evf6h0","namespace":"camel-system"},"namespace":"camel-system","name":"kit-cgn8vko2ed2c73evf6h0","reconcileID":"2234bf9d-e4b5-449d-9b32-394e47f3712a","error":"command terminated with exit code 126","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:326\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:234"}
@squakez squakez added the kind/bug Something isn't working label Apr 11, 2023
@squakez
Copy link
Contributor

squakez commented Apr 12, 2023

I think this problem is because of the kill command is not available in the builder Pod which now is created from Mandrel:

OCI runtime exec failed: exec failed: unable to start container process: exec: "kill": executable file not found in $PATH: unknown

@squakez squakez self-assigned this Apr 12, 2023
@squakez squakez added this to the 2.0.0 milestone Apr 12, 2023
squakez added a commit to squakez/camel-k that referenced this issue Apr 13, 2023
The builder Pods may not have a /bin/kill command, but do have a builtin shell kill command available.

Closes apache#4241
squakez added a commit that referenced this issue Apr 13, 2023
The builder Pods may not have a /bin/kill command, but do have a builtin shell kill command available.

Closes #4241
squakez added a commit to squakez/camel-k that referenced this issue Jun 5, 2023
The builder Pods may not have a /bin/kill command, but do have a builtin shell kill command available.

Closes apache#4241
squakez added a commit that referenced this issue Jun 6, 2023
The builder Pods may not have a /bin/kill command, but do have a builtin shell kill command available.

Closes #4241
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants