Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates to match kubernetes 'charts' repo #59

Merged
merged 8 commits into from
Feb 1, 2018
Merged

Updates to match kubernetes 'charts' repo #59

merged 8 commits into from
Feb 1, 2018

Conversation

some-ibmer
Copy link
Contributor

These changes need to go in to match the kubernetes charts repostory. I'm currently seeing the following when using deploy_charts.sh, @mrshah-at-ibm / @dhyey-ibm, can either of you take a look?

deploy_charts.sh: error: the following pods failed with errors:
channel-ibm-blockchain-channel-create                       0/2       Error       0          30s

$ kubectl logs channel-ibm-blockchain-channel-create createchanneltx
/shared
bootstrapped
cas
configtx.yaml
crypto-config
keepalived
orderer.block
status_fabricca_complete
status_orderer_complete
status_org1peer1_complete
status_org2peer1_complete
zombie_container_list.txt
zombie_new_container_list.txt
zombie_old_container_list.txt
2018-01-08 15:27:59.506 UTC [common/configtx/tool] main -> INFO 001 Loading configuration
2018-01-08 15:27:59.513 UTC [common/configtx/tool] doOutputChannelCreateTx -> INFO 002 Generating new channel configtx
2018-01-08 15:27:59.514 UTC [common/configtx/tool] doOutputChannelCreateTx -> INFO 003 Writing new channel tx

$ kubectl logs channel-ibm-blockchain-channel-create createchannel
2018-01-08 15:28:00.068 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2018-01-08 15:28:00.068 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-01-08 15:28:20.069 UTC [grpc] Printf -> DEBU 003 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing dial tcp 172.21.107.243: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
Usage:
  peer channel create [flags]

Flags:
  -c, --channelID string   In case of a newChain command, the channel ID to create.
  -f, --file string        Configuration transaction file generated by a tool such as configtxgen for submitting to orderer
  -t, --timeout int        Channel creation timeout (default 5)

Global Flags:
      --cafile string              Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --logging-level string       Default logging level and overrides, see core.yaml for full syntax
  -o, --orderer string             Ordering service endpoint
      --test.coverprofile string   Done (default "coverage.cov")
      --tls                        Use TLS when communicating with the orderer endpoint
  -v, --version                    Display current version of fabric peer server

@mrshah-at-ibm
Copy link

@eddie-at-ibm looks like create-channel pod is not able to connect to the orderer pod. It might be starting before the orderer pod comes up.

This is a good start though. We can work on the create channel pod once these changes are merged. Can you fix the merge conflicts and I will merge this PR.

Thanks for the PR!

@some-ibmer
Copy link
Contributor Author

@mrshah-at-ibm, merge conflicts are resolved now.

@mrshah-at-ibm mrshah-at-ibm merged commit 0a71319 into IBM-Blockchain-Archive:master Feb 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants