mirrord: exec panic auth error aws
Bug Description
Running mirrord exec
with kubeconfig set to execute aws command to get token, fails with panic.
Steps to Reproduce
- Create EKS cluster
- Run
aws eks update-kubeconfig --name test-cluster --alias test-cluster
- Run
mirrord exec ...
Backtrace
thread '<unnamed>' panicked at 'failed to create agent in k8s: mirrord-layer: Kube failed with error `auth error: auth exec command '"aws" "--region" "us-east-1" "eks" "get-token" "--cluster-name" "development-cluster"' failed with status signal: 6 (SIGABRT) (core dumped): Output { status: ExitStatus(unix_wait_status(134)), stdout: "", stderr: "thread '<unnamed>' panicked at 'failed to create agent in k8s: mirrord-layer: Kube failed with error `auth error: auth exec command '\"aws\" \"--region\" \"us-east-1\" \"eks\" \"get-token\" \"--cluster-name\" \"development-cluster\"' failed with status signal: 6 (SIGABRT) (core dumped): Output { status: ExitStatus(unix_wait_status(134)), stdout: \"\", stderr: \"thread '<unnamed>' panicked at 'failed to create agent in k8s: mirrord-layer: Kube failed with error `auth error: auth exec command '\\\"aws\\\" \\\"--region\\\" \\\"us-east-1\\\" \\\"eks\\\" \\\"get-token\\\" \\\"--cluster-name\\\" \\\"development-cluster\\\"' failed with status signal: 11 (SIGSEGV) (core dumped): Output { status: ExitStatus(unix_wait_status(139)), stdout: \\\"\\\", stderr: \\\"\\\\r\\\\nmalloc: unknown:0: assertion botched\\\\r\\\\nmalloc: block on free list clobbered\\\\nAborting...\\\" }`!', mirrord-layer/src/connection.rs:92:18\\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\\nfatal runtime error: failed to initiate panic, error 5\\n\" }`!', mirrord-layer/src/connection.rs:92:18\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\nfatal runtime error: failed to initiate panic, error 5\n" }`!', mirrord-layer/src/connection.rs:92:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
Relevant Logs
No response
Your operating system and version
Manjaro Linux
Local process
Bourne-Again shell script, ASCII text executable
Local process version
No response
Additional Info
mirrord 3.0.19-alpha
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (10 by maintainers)
Commits related to this issue
- Skip loading mirrord env var (#552) ### Changed - CI: mirrord-layer UT and integration run in same job. - .devcontainer: Added missing dependencies and also kind for running e2e tests. ### Fixed... — committed to metalbear-co/mirrord by aviramha 2 years ago
- Skip loading mirrord env var (#552) ### Changed - CI: mirrord-layer UT and integration run in same job. - .devcontainer: Added missing dependencies and also kind for running e2e tests. ### Fixed... — committed to metalbear-co/mirrord by aviramha 2 years ago
- Skip loading mirrord env var (#552) ### Changed - CI: mirrord-layer UT and integration run in same job. - .devcontainer: Added missing dependencies and also kind for running e2e tests. ### Fixed... — committed to metalbear-co/mirrord by aviramha 2 years ago
- Fixed Issue [#531](https://github.com/metalbear-co/mirrord/issues/531). We now detect NixOS/Devbox usage and add `sh` to skipped list. — committed to aviramha/mirrord by aviramha 2 years ago
- Fixed Issue #531 (#573) ### Fixed Issue [#531](https://github.com/metalbear-co/mirrord/issues/531). We now detect NixOS/Devbox usage and add `sh` to skipped list. Co-authored-by: Aviram Hassan <avi... — committed to metalbear-co/mirrord by aviramha 2 years ago
- Fixed Issue #531 (#573) ### Fixed Issue [#531](https://github.com/metalbear-co/mirrord/issues/531). We now detect NixOS/Devbox usage and add `sh` to skipped list. Co-authored-by: Aviram Hassan <avi... — committed to metalbear-co/mirrord by aviramha 2 years ago
@aviramha sorry for the slow response. It does seem to work now 😃
Took me some time but I managed to reproduce it: