Issue creating a channel after deploying the network.

[alexvicegrab]

After installing the ibm-composer-network, I attempt to login into one of the peers:

kubectl exec -it cloying-panther-ibm-blockchain-network-org1peer1-77d6fdc95nkjpp -- sh

and create a channel:

# peer channel create -o $ORDERER_URL -c composerchannel -f ./composer-channel.tx
2018-03-19 21:10:46.912 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2018-03-19 21:10:46.912 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-03-19 21:11:06.913 UTC [grpc] Printf -> DEBU 003 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing dial tcp 10.0.138.157:31010: i/o timeout"; Reconnecting to {ibm-blockchain-network-orderer:31010 <nil>}
Error: Error connecting due to  rpc error: code = Unavailable desc = grpc: the connection is unavailable

I'm using the $ORDERER_URL env, which points to the orderer service and its open port.

This command works fine when working locally with docker-compose examples.

What steps can I take to debug this?

Thank you!

[alexvicegrab]

Solved this issue on my cluster by replacing the NodePort services with ClusterIP.

Either Azure AKS does not support NodePorts by default, or blocks the traffic there. Best solution is to use ClusterIP services and link them all to an Ingress, I think.

[mrshah-at-ibm]

NodePort service should also create a ClusterIP address. Not sure why it didn't work. Glad it worked for you. Thanks for the update.