Error in install

[dallasvaughan]

I'm getting the following when attempting to install using the plugin:

Caused by: io.grpc.StatusRuntimeException: UNAVAILABLE: Network closed for unknown reason
    at io.grpc.Status.asRuntimeException (Status.java:526)
    at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose (ClientCalls.java:467)
    at io.grpc.ForwardingClientCallListener.onClose (ForwardingClientCallListener.java:41)
    at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose (CensusStatsModule.java:684)
    at io.grpc.ForwardingClientCallListener.onClose (ForwardingClientCallListener.java:41)
    at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose (CensusTracingModule.java:391)
    at io.grpc.internal.ClientCallImpl.closeObserver (ClientCallImpl.java:475)
    at io.grpc.internal.ClientCallImpl.access$300 (ClientCallImpl.java:63)
    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close (ClientCallImpl.java:557)
    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600 (ClientCallImpl.java:478)
    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext (ClientCallImpl.java:590)
    at io.grpc.internal.ContextRunnable.run (ContextRunnable.java:37)
    at io.grpc.internal.SerializingExecutor.run (SerializingExecutor.java:123)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)

Everything is set up correctly in my environment with respect to helm/kubernetes, i.e., I can successfully run helm install from the command line so theoretically the plugin should succeed since it's running in the same environment.

Is there any way to print out more logs to debug what kubernetes configuration it's using to try and connect?

[ljnelson]

There are several levels of logging:

• Logging done by the plugin itself
• Logging done by the microBean Helm project itself
• Logging done by the generated code (if any)
• Logging done by the fabric8 Kubernetes Client used to attach to Kubernetes
• Logging done by the gRPC Java framework used by the generated code to talk to the gRPC Tiller endpoints

Offhand I would look at the https://github.com/grpc/grpc-java project to see how they do logging, since you probably want to see what's going on in their io.grpc.internal.ClientCallImpl class. (Obviously I have no control over this in this project.)

[dallasvaughan]

Thanks for the quick replies @ljnelson. Might be because we're using helm 2.13.0 which may not be compatible :-/.

[ljnelson]

Oh, I see; interesting. I would think Tiller version 2.13.0 would be able to handle version strings less than that. To test, try using the helm client at a lesser version than the version of Tiller you have installed. If that works, then this is not the problem.