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

Somewhere (!) there's a hard-binding to 'blockchain-orderer:31010` #99

Open DazWilkin opened 6 years ago

DazWilkin commented 6 years ago

...and it's been driving me NUTS! :-)

The Helm Chart produces nicely-named resources of the form ibm-blockchain-network-X

However, deploying the Helm Chart as-is throws recurring (red-herring?) errors of the form:

[grpc] Printf -> DEBU e9a[0m grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing dial tcp: lookup blockchain-orderer on 10.19.240.10:53: no such host"; Reconnecting to {blockchain-orderer:31010 <nil>}

I assumed (incorrectly) that I'd missed a name value somewhere in the templates but after extensively reviewing deployments created by the Helm Chart (both the templates and the generated YAML to prove I am not going mad) and purely from the scripts, both exhibit this behavior and I'm entirely unable to find the source of the name blockchain-orderer:31010. It's particularly elusive because the correct port is associated with the address; this kept me too long thinking it was originating in the templates somehow.

I would expect ibm-blockchain-network-orderer:31010.

Every other reference appears to work when correctly apart from this and it's made by both the Peers (org1peer1 and org2peer1) logs will include the error.

By renaming the Helm Chart deployment to blockchain, I can have the Chart create an Orderer Service called blockchain-orderer and then the issue disappears.

Curiously, it doesn't appear to break the network but it can't be good for it (or me!) ;-)

mrshah-at-ibm commented 6 years ago

@DazWilkin as you can tell we have been a bit busy with some stuff here.. We will get back on this early next week.. Sorry for the trouble.

DazWilkin commented 6 years ago

@mrshah-at-ibm -- There's no need to apologize but it's appreciated! You folks got me much further along than I would have been had I started from scratch. My feedback is intended to help others that use your repo to avoid similar pitfalls.

I'm still stuck getting Composer working on the back of the Helm Chart (https://github.com/IBM-Blockchain/ibm-container-service/issues/98) but, if I use the scripts entirely, it works. I'll spend time today reconciling the two.

Once I'm able to get everything working, as committed, I'll submit a PR back to you.