Closed pshgpt closed 1 year ago
Running this command : kubectl hlf ordnode join --block=mychannel.block --name=orderer-node1 --identity=admin-tls-ordservice.yaml --namespace=default
Error: Post "https://143.244.138.201:0/participation/v1/channels": dial tcp 143.244.138.201:0: connect: connection timed out
Status code=201
kubectl hlf ordnode join --block=mychannel.block --name=orderer-node1 --identity=admin-tls-ordservice.yaml --namespace=default
No response
pool-mxjx1jwnv-fa6xb Ready 60m v1.27.2 10.122.0.3 143.244.138.201 Debian GNU/Linux 11 (bullseye) 6.1.0-0.deb11.6-amd64 containerd://1.6.20 pool-mxjx1jwnv-fa6xr Ready 60m v1.27.2 10.122.0.2 143.244.138.114 Debian GNU/Linux 11 (bullseye) 6.1.0-0.deb11.6-amd64 containerd://1.6.20
Are you using Istio?
@dviejokfs yes I'm
Can someone help on this issue?
Please check the Orderer CRD, it doesn't has the port configured correctly.
What happened?
Running this command : kubectl hlf ordnode join --block=mychannel.block --name=orderer-node1 --identity=admin-tls-ordservice.yaml --namespace=default
Error: Post "https://143.244.138.201:0/participation/v1/channels": dial tcp 143.244.138.201:0: connect: connection timed out
What did you expect to happen?
Status code=201
How can we reproduce it (as minimally and precisely as possible)?
kubectl hlf ordnode join --block=mychannel.block --name=orderer-node1 --identity=admin-tls-ordservice.yaml --namespace=default
Anything else we need to know?
No response
Kubernetes version
pool-mxjx1jwnv-fa6xb Ready 60m v1.27.2 10.122.0.3 143.244.138.201 Debian GNU/Linux 11 (bullseye) 6.1.0-0.deb11.6-amd64 containerd://1.6.20
pool-mxjx1jwnv-fa6xr Ready 60m v1.27.2 10.122.0.2 143.244.138.114 Debian GNU/Linux 11 (bullseye) 6.1.0-0.deb11.6-amd64 containerd://1.6.20