You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"}
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: