我正在尝试在kubernetes(本地在minikube上)上设置Fabric v2.0测试网络(https://hyperledger-fabric.readthedocs.io/en/release-2.0/test_network.html)。我有一个错误,peer channel join
。
我根据测试网络的docker-compose-test-net.yaml创建了kubernetes文件。我成功部署了以下Pod:
我已成功使用cryptogen和configtxgen生成了加密材料。
我成功创建了频道:当我在织物工具箱中时:
bash-5.0# peer channel create -o orderer-example-com:7050 -c $CHANNEL_NAME --ordererTLSHostnameOverride orderer.example.com -f /fabric/${CHANNEL_NAME}.tx --tls --cafile $ORDERER_CA
2020-02-11 08:10:14.057 CET [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2020-02-11 08:10:14.080 CET [cli.common] readBlock -> INFO 002 Expect block, but got status: &{NOT_FOUND}
...
2020-02-11 08:10:15.105 CET [cli.common] readBlock -> INFO 00c Received block: 0
但是当我尝试第一个对等加入频道时,出现错误。我已经花了几天时间,但找不到解决方案。您的帮助将不胜感激!
在布料工具窗格中:
bash-5.0# peer channel join -b $CHANNEL_NAME.block
Error: error getting endorser client for channel: endorser client failed to connect to peer0-org1-example-com:7051: failed to create new connection: context deadline exceeded
我在peer0-org1-example-com pod日志中看到的内容:
[31m2020-02-11 08:11:29.945 CET [core.comm] ServerHandshake -> ERRO 1b9[0m TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.17.0.6:43270
[36m2020-02-11 08:11:29.945 CET [grpc] handleRawConn -> DEBU 1ba[0m grpc: Server.Serve failed to complete security handshake from "172.17.0.6:43270": remote error: tls: bad certificate
谢谢!
更新:
如果直接在peer0-org1-example-com窗格上运行对等通道加入,则可以看到存在证书问题:
addrConn.createTransport failed to connect to {peer0-org1-example-com:7051 0 <nil>}. Err :connection error: desc = "transport: authentication handshake failed: x509: certificate is valid for peer0.org1.example.com, peer0, localhost, peer0.org1.example.com, peer0, localhost, peer0.org1.example.com, peer0, localhost, not peer0-org1-example-com". Reconnecting.
似乎它会接受peer0.org1.example.com的连接,但不接受peer0-org1-example-com的连接。但是在Kubernetes中,不允许我在服务和部署的名称中加点,这就是为什么要用破折号。你知道如何解决这个问题吗?我试图使cryptogen工具为peer0-org1-example-com生成证书,但事情搞砸了。我认为最好用点来命名kubernetes,但我似乎做不到。
对等部署文件中的名称:
apiVersion: apps/v1
kind: Deployment
metadata:
name: peer0-org1-example-com
spec:
selector:
matchLabels:
name: peer0-org1-example-com
replicas: 1
template:
metadata:
labels:
name: peer0-org1-example-com
对等服务文件中的名称:
apiVersion: v1
kind: Service
metadata:
name: peer0-org1-example-com
labels:
run: peer0-org1-example-com
spec:
type: ClusterIP
selector:
name: peer0-org1-example-com
ports:
- protocol: TCP
port: 7051
name: grpc
我们在OpenShift中有类似的点/破折号证书问题,并通过在我们的crypto-config文件中为每个主机设置带破折号的CommonName来解决。也许这也对您有用。
类似这样的东西:
PeerOrgs:
- Name: Org1
Domain: org1-example-com
EnableNodeOUs: true
Specs:
- Hostname: peer0
CommonName: "peer0-org1-example-com"
- Hostname: peer1
CommonName: "peer1-org1-example-com"
CA:
Hostname: ca
CommonName: "ca-org1-example-com"
PeerOrgs:
- Name: Org2
Domain: org2-example-com
EnableNodeOUs: true
Specs:
- Hostname: peer0
CommonName: "peer0-org2-example-com"
- Hostname: peer1
CommonName: "peer1-org2-example-com"
CA:
Hostname: ca
CommonName: "ca-org2-example-com"
OrdererOrgs:
- Name: Orderer
Domain: example.com
EnableNodeOUs: true
Specs:
- Hostname: orderer
CommonName: "orderer-example-com"
更新:我们还更改了configtx.yaml中的所有点地址,如下所示:
Orderer: &OrdererDefaults
...
EtcdRaft:
Consenters:
- Host: orderer-example-com
...
Addresses:
- orderer-example-com:7050