search

IBM-Blockchain-Archive / ibm-container-service

IBM Blockchain Platform for Developers on IBM Container Service
Apache License 2.0
89 stars 74 forks source link

Channel create fails during chart deployment #74

Closed timroster closed 6 years ago

timroster commented 6 years ago

Commit 0a713198 reverts container images to earlier versions in the templates to 1.0.0 . This causes deployment to fail in the channel creation step with an error like:

2018-02-08 04:35:07.067 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2018-02-08 04:35:07.067 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-02-08 04:35:27.068 UTC [grpc] Printf -> DEBU 003 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing dial tcp 172.21.131.152: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

Suggested fix: update container image tags across component values.yaml to known best versions.

mrshah-at-ibm commented 6 years ago

We should remove channel creation, channel join, chaincode actions & transactions from helm charts. We should use helm-charts to setup the network only.

We will work on this.

mrshah-at-ibm commented 6 years ago

76 removes the chaincode and composer stuff from the helm-charts. The helm-charts should be used to setup the network and rest should be done by the scripts or manually.

Closing this.

alexvicegrab commented 6 years ago

I have the same issue when doing this manually with the latest network:

kubectl exec -it cloying-panther-ibm-blockchain-network-org1peer1-77d6fdc95nkjpp -- sh
# 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

How can I solve this connectivity issue?

mrshah-at-ibm commented 6 years ago

@alexvicegrab can you check if the name of the service for the Orderer is ibm-blockchain-network-orderer ?