Re: #fabric-questions LifecycleEndorsement with signature policy: ENDORSEMENT_FAILURE #fabric-questions

Nikhil Gupta

Hi Mattia,

The chaincode definition approval is stored on your peer. The commit transaction is similar to a chaincode transaction in that it queries your peers to get the required endorsements.


-----fabric@... wrote: -----
To: fabric@...
From: "Mattia Bolzonella"
Sent by: fabric@...
Date: 05/04/2020 03:57AM
Subject: [EXTERNAL] [Hyperledger Fabric] #fabric-questions LifecycleEndorsement with signature policy: ENDORSEMENT_FAILURE

I've specified a policy for the LifecycleEndorsement in my configtx.yaml and it is:
         Type: Signature
         Rule: "OR('MyOrgMSP.admin')"
But when I try to commit the chaincode I get ENDORSEMENT_FAILURE in the peer logs because the identity being evaluated is the peer identity. How can I get the admin identity to be evaluated? The cli, from which I execute the commit command, has CORE_PEER_MSPCONFIGPATH  set to the org admin folder.
The chaincode is approved only by MyOrg (and I expect that is enough considering the LifecycleEndorsement policy)

Join to automatically receive all group messages.