Re: Endorsement Policy Failure while committing chaincode #fabric-kubernetes #hyperledger-fabric #chaincode


Arsh
 

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 setup, only 4 orgs are joining the certificate channel who will be using the chaincode on that channel and hence the reason behind the commit readiness command showing approval of only 4 orgs and not 8 orgs with 4 orgs set to false. Atleast that was what I was thinking as the reason behind it. So in that case, isn't the MAJORITY already achieved? 4/4 ?

channels:
    - name: certificatechannel
      # all peers in these organizations will join the channel
      orgs: [Ni, Schooleducation, Highereducation, Es]
    - name: registrationchannel
      # all peers in these organizations will join the channel
      orgs: [Ni, Igr]
chaincodes:
    - name: cc
      # if defined, this will override the global chaincode.version value
      version: #"1.0"
      # chaincode will be installed to all peers in these organizations
      orgs: [Ni, Igr, Schooleducation, Highereducation, Es]
      # at which channels are we instantiating/upgrading chaincode?
      channels:
      - name: certificatechannel
        # chaincode will be instantiated/upgraded using the first peer in the first organization
        # chaincode will be invoked on all peers in these organizations
        orgs: [Ni, Schooleducation, Highereducation, Es]
      - name: registrationchannel
        # chaincode will be instantiated/upgraded using the first peer in the first organization
        # chaincode will be invoked on all peers in these organizations
        orgs: [Ni, Igr]

Join fabric@lists.hyperledger.org to automatically receive all group messages.