Snow create fails with minikube
Opened this issue · 0 comments
Running snow create I get the following error after the cli runs the command helm init --debug --tiller-tls --tiller-tls-cert $(helm home)/tiller.cert.pem --tiller-tls-key $(helm home)/tiller.key.pem --tiller-tls-verify --tls-ca-cert $(helm home)/ca.cert.pem --service-account tiller --wait.
I used a fresh install of minikube. Host is linux.
[...]
$HELM_HOME has been configured at /home/sean/.helm.
Warning: Tiller is already installed in the cluster.
(Use --client-only to suppress this message, or --upgrade to upgrade Tiller to the current version.)
[debug] Created tunnel using local port: '44751'
[debug] SERVER: "127.0.0.1:44751"
[debug] Host="", Key="/home/sean/.helm/tiller.key.pem", Cert="/home/sean/.helm/tiller.cert.pem", CA="/home/sean/.helm/ca.cert.pem"
E0308 11:39:20.148106 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:20 socat[8082] E write(6, 0x9c4d70, 7): Broken pipe
E0308 11:39:21.154867 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:21 socat[8086] E write(6, 0x1d49d70, 7): Broken pipe
E0308 11:39:22.571203 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:22 socat[8087] E write(6, 0xbf1d70, 7): Broken pipe
E0308 11:39:24.794152 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:24 socat[8137] E write(6, 0x153bd70, 7): Broken pipe
E0308 11:39:29.434909 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:29 socat[8192] E write(6, 0x14b2d70, 7): Broken pipe
E0308 11:39:35.314530 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:35 socat[8251] E write(6, 0x6f9d70, 7): Broken pipe
E0308 11:39:46.213001 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:46 socat[8313] E write(6, 0x6a6d70, 7): Broken pipe
E0308 11:40:04.233060 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:40:04 socat[8511] E write(6, 0x21ddd70, 7): Broken pipe
E0308 11:40:29.592959 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:40:29 socat[8689] E write(6, 0x885d70, 7): Broken pipe
E0308 11:41:06.253659 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:41:06 socat[9007] E write(6, 0xd85d70, 7): Broken pipe
E0308 11:42:24.617551 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:42:24 socat[9604] E write(6, 0x12c7d70, 7): Broken pipe
Error: could not ping Tiller: context deadline exceeded
Command failed:
helm init --debug --tiller-tls --tiller-tls-cert
E0308 11:39:20.148106 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:20 socat[8082] E write(6, 0x9c4d70, 7): Broken pipe
E0308 11:39:21.154867 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:21 socat[8086] E write(6, 0x1d49d70, 7): Broken pipe
E0308 11:39:22.571203 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:22 socat[8087] E write(6, 0xbf1d70, 7): Broken pipe
E0308 11:39:24.794152 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:24 socat[8137] E write(6, 0x153bd70, 7): Broken pipe
E0308 11:39:29.434909 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:29 socat[8192] E write(6, 0x14b2d70, 7): Broken pipe
E0308 11:39:35.314530 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:35 socat[8251] E write(6, 0x6f9d70, 7): Broken pipe
E0308 11:39:46.213001 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:46 socat[8313] E write(6, 0x6a6d70, 7): Broken pipe
E0308 11:40:04.233060 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:40:04 socat[8511] E write(6, 0x21ddd70, 7): Broken pipe
E0308 11:40:29.592959 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:40:29 socat[8689] E write(6, 0x885d70, 7): Broken pipe
E0308 11:41:06.253659 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:41:06 socat[9007] E write(6, 0xd85d70, 7): Broken pipe
E0308 11:42:24.617551 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:42:24 socat[9604] E write(6, 0x12c7d70, 7): Broken pipe
Error: could not ping Tiller: context deadline exceeded
Error: Command failed:
helm init --debug --tiller-tls --tiller-tls-cert
E0308 11:39:20.148106 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:20 socat[8082] E write(6, 0x9c4d70, 7): Broken pipe
E0308 11:39:21.154867 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:21 socat[8086] E write(6, 0x1d49d70, 7): Broken pipe
E0308 11:39:22.571203 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:22 socat[8087] E write(6, 0xbf1d70, 7): Broken pipe
E0308 11:39:24.794152 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:24 socat[8137] E write(6, 0x153bd70, 7): Broken pipe
E0308 11:39:29.434909 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:29 socat[8192] E write(6, 0x14b2d70, 7): Broken pipe
E0308 11:39:35.314530 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:35 socat[8251] E write(6, 0x6f9d70, 7): Broken pipe
E0308 11:39:46.213001 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:46 socat[8313] E write(6, 0x6a6d70, 7): Broken pipe
E0308 11:40:04.233060 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:40:04 socat[8511] E write(6, 0x21ddd70, 7): Broken pipe
E0308 11:40:29.592959 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:40:29 socat[8689] E write(6, 0x885d70, 7): Broken pipe
E0308 11:41:06.253659 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:41:06 socat[9007] E write(6, 0xd85d70, 7): Broken pipe
E0308 11:42:24.617551 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:42:24 socat[9604] E write(6, 0x12c7d70, 7): Broken pipe
Error: could not ping Tiller: context deadline exceeded
at ChildProcess.exithandler (child_process.js:281:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:915:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)(node:20869) UnhandledPromiseRejectionWarning: Error: Command failed:
helm init --debug --tiller-tls --tiller-tls-cert $(helm home)/tiller.cert.pem --tiller-tls-key $(helm home)/tiller.key.pem --tiller-tls-verify --tls-ca-cert $(helm home)/ca.cert.pem --service-account tiller --wait
E0308 11:39:20.148106 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:20 socat[8082] E write(6, 0x9c4d70, 7): Broken pipe
E0308 11:39:21.154867 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:21 socat[8086] E write(6, 0x1d49d70, 7): Broken pipe
E0308 11:39:22.571203 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:22 socat[8087] E write(6, 0xbf1d70, 7): Broken pipe
E0308 11:39:24.794152 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:24 socat[8137] E write(6, 0x153bd70, 7): Broken pipe
E0308 11:39:29.434909 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:29 socat[8192] E write(6, 0x14b2d70, 7): Broken pipe
E0308 11:39:35.314530 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:35 socat[8251] E write(6, 0x6f9d70, 7): Broken pipe
E0308 11:39:46.213001 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:39:46 socat[8313] E write(6, 0x6a6d70, 7): Broken pipe
E0308 11:40:04.233060 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:40:04 socat[8511] E write(6, 0x21ddd70, 7): Broken pipe
E0308 11:40:29.592959 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:40:29 socat[8689] E write(6, 0x885d70, 7): Broken pipe
E0308 11:41:06.253659 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:41:06 socat[9007] E write(6, 0xd85d70, 7): Broken pipe
E0308 11:42:24.617551 23753 portforward.go:391] an error occurred forwarding 44751 -> 44134: error forwarding port 44134 to pod ec9d135897e3f2d28fcc493b858326d1eee447f2cc007fd8b012b20403dbc148, uid : exit status 1: 2019/03/08 10:42:24 socat[9604] E write(6, 0x12c7d70, 7): Broken pipe
Error: could not ping Tiller: context deadline exceeded
at ChildProcess.exithandler (child_process.js:281:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:915:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
(node:20869) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:20869) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.