You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/07/18 20:14:44 UTC
[GitHub] [camel-k] MotaOcimar opened a new issue, #3456: `camel-k-operator` pod in `CrashLoopBackOff`
MotaOcimar opened a new issue, #3456:
URL: https://github.com/apache/camel-k/issues/3456
I'm following the [documentation procedure](https://camel.apache.org/camel-k/1.9.x/installation/installation.html#procedure) and [enabling the registration add-on in minikube](https://camel.apache.org/camel-k/1.9.x/installation/platform/minikube.html).
So I'm running
```sh
minikube start --addons registry
kamel install
```
to start the cluster and install Camel K into it.
But when I run `kubectl get pod` I get `CrashLoopBackOff` as the `camel-k-operator` status.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3456: `camel-k-operator` pod in `CrashLoopBackOff`
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3456:
URL: https://github.com/apache/camel-k/issues/3456#issuecomment-1189123023
Thanks. You've hit #3348. Please, follow that issue where some workaround is described. The main root cause will eventually get fixed on some dependency upgrade.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3456: `camel-k-operator` pod in `CrashLoopBackOff`
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3456:
URL: https://github.com/apache/camel-k/issues/3456#issuecomment-1188705145
We must understand why it is failing. Can you run:
```
kubectl get events | grep camel-k-operator
```
we may see the reason of the failure. If the pod manages to start and it is some application failure, it could be interesting looking at the crashed pod log via:
```
kubectl logs [podname] -p
```
Please, report the output here and we'll try to help.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] MotaOcimar commented on issue #3456: `camel-k-operator` pod in `CrashLoopBackOff`
Posted by GitBox <gi...@apache.org>.
MotaOcimar commented on issue #3456:
URL: https://github.com/apache/camel-k/issues/3456#issuecomment-1189400211
Thanks!
Using the hyperv driver instead of docker worked for me.
Closing this issue in favor of #3348
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] MotaOcimar closed issue #3456: `camel-k-operator` pod in `CrashLoopBackOff`
Posted by GitBox <gi...@apache.org>.
MotaOcimar closed issue #3456: `camel-k-operator` pod in `CrashLoopBackOff`
URL: https://github.com/apache/camel-k/issues/3456
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] MotaOcimar commented on issue #3456: `camel-k-operator` pod in `CrashLoopBackOff`
Posted by GitBox <gi...@apache.org>.
MotaOcimar commented on issue #3456:
URL: https://github.com/apache/camel-k/issues/3456#issuecomment-1189036052
`kubectl get events` gave me the following:
```
LAST SEEN TYPE REASON OBJECT MESSAGE
7m9s Normal Scheduled pod/camel-k-operator-848fd8785b-cr9pp Successfully assigned default/camel-k-operator-848fd8785b-cr9pp to minikube
7m5s Normal Pulling pod/camel-k-operator-848fd8785b-cr9pp Pulling image "docker.io/apache/camel-k:1.9.2"
2m23s Normal Pulled pod/camel-k-operator-848fd8785b-cr9pp Successfully pulled image "docker.io/apache/camel-k:1.9.2" in 4m45.3178036s
42s Normal Created pod/camel-k-operator-848fd8785b-cr9pp Created container camel-k-operator
42s Normal Started pod/camel-k-operator-848fd8785b-cr9pp Started container camel-k-operator
43s Normal Pulled pod/camel-k-operator-848fd8785b-cr9pp Container image "docker.io/apache/camel-k:1.9.2" already present on machine
55s Warning BackOff pod/camel-k-operator-848fd8785b-cr9pp Back-off restarting failed container
7m9s Normal SuccessfulCreate replicaset/camel-k-operator-848fd8785b Created pod: camel-k-operator-848fd8785b-cr9pp
7m9s Normal ScalingReplicaSet deployment/camel-k-operator Scaled up replica set camel-k-operator-848fd8785b to 1
```
Running `kubectl logs [podname] -p` I get
```json
{
"level": "error",
"ts": 1658235623.4016757,
"logger": "cmd",
"msg": "failed to set GOMAXPROCS from cgroups",
"error": "path \"/docker/ec4a100d598f3529dbcc3a9364c8caceb32abd8c11632456d58c7948bb756d36\" is not a descendant of mount point root \"/docker/ec4a100d598f3529dbcc3a9364c8caceb32abd8c11632456d58c7948bb756d36/kubelet\" and cannot be exposed from \"/sys/fs/cgroup/rdma/kubelet\"",
"stacktrace": "github.com/apache/camel-k/pkg/cmd.(*operatorCmdOptions).run\n\tgithub.com/apache/camel-k/pkg/cmd/operator.go:57\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.4.0/command.go:860\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.4.0/command.go:974\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.4.0/command.go:902\nmain.main\n\tcommand-line-arguments/main.go:47\nruntime.main\n\truntime/proc.go:225"
}
```
Formatting the stacktrace we get:
```
github.com/apache/camel-k/pkg/cmd.(*operatorCmdOptions).run
github.com/apache/camel-k/pkg/cmd/operator.go:57
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.4.0/command.go:860
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.4.0/command.go:974
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.4.0/command.go:902
main.main
command-line-arguments/main.go:47
runtime.main
runtime/proc.go:225
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org