I am trying to update system channel configuration to add a new consortium. I have placed the org admin signcert in the map/admincerts folder. the system channel update is failing with the following e

#fabric-kubernetes #signcerts #x509 #organizations #orderer

Hello, I have a HLF running on azure AKS cluster. I have a couchdb acting as a wallet to store the identities of the blockchain admin and users. It is hosted along with all the other pods. when i crea

#couchdb #fabric-kubernetes #hyperledger-fabric #kubernetes #fabric-sdk-node

The system is working now. documenting just in case if any1 in future facing the same errors which I faced. 1)while doing a system channel update if you face the below error, check your admin cert in

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Thanks Satheesh, it worked. I had to specify the relative path for the tls cert, I was specifying the absolute path. now I am trying to edit system channel and getting the following error. any idea ab

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

orderer host need to be fully qualified with domain name. And if orderer is running on a different host, you need to provide that instead of locallhost along with port number where orderer is listenin

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

thanks for the reply Satheesh. I tried the suggestion. the orderer name is just orderer0 so instead of orderer.example.com, I have used just orderer0. (this is correct right?). the error still persist

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

you need to pass orderer details as well: for e.g., -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Hey guys, overview of the problem i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info. I am

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

I would like to mention that this setup is spread between 2 clusters, I am exposing services between clusters to interconnect using skupper. the current running blockchain is on azure central India cl

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Hey guys, overview of the problem i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info. I am

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

@Dave, Yes the NodeOUs are also configured. The logs state that the sub-policies are not being satisfied but there is evidently no such thing in the configtx.yaml which indicates/backs the claim. How

#fabric-kubernetes #hyperledger-fabric #chaincode

@Josh, I would love to see if fabric-operator and k8s-builder lifecycle make my life any easier. Need to find time to test them. Also, will keep my investigation of finding what went wrong with the fa

#fabric-kubernetes #hyperledger-fabric #chaincode

You can use either OrgMSP.member or OrgMSP.peer format, assuming you’ve configured the MSP for Node OU roles and provided the matching OU “peer” tag in the peer’s certificate. More details at https://

#fabric-kubernetes #hyperledger-fabric #chaincode

Argo provides an incredible workflow engine for Kubernetes. It is _more_ than enough to handle the workloads of running Fabric CLI binaries - you are on a solid course for workflow automation! Regardi

#fabric-kubernetes #hyperledger-fabric #chaincode

@Dave As you can see from the configtx.yaml that I've previously shared, all the orgs have LifecycleEndorsement policy set to Endorsement: Type: Signature Rule: "OR('Org1MSP.peer')" and from the examp

#fabric-kubernetes #hyperledger-fabric #chaincode

Arsh / Dave - a couple of questions: Arsh I don't recognize the yaml syntax where you are describing your network. Is this a descriptive format that you built in-house, or an input grammar supported b

#fabric-kubernetes #hyperledger-fabric #chaincode

Here is the key lines: 2022-06-22 07:16:04.421 UTC [policies] func1 -> DEBU 777c66 Evaluation Failed: Only 0 policies were satisfied, but needed 3 of [ SchooleducationMSP/Endorsement HighereducationMS

#fabric-kubernetes #hyperledger-fabric #chaincode

These are the logs from one of the peers of an org.

#fabric-kubernetes #hyperledger-fabric #chaincode

Thanks David, that was precisely what I was pondering over too but I would like to provide you a piece of information here. I'm using two channels and the network setup is as shown below. As per the s

#fabric-kubernetes #hyperledger-fabric #chaincode

Hi Josh, thank you for your quick response, I'd love to explore the new fabric-operator. However, I'm still intrigued as to what might have caused the error above mentioned. It is working fine in my d

#fabric-kubernetes #hyperledger-fabric #chaincode