'checkcommitreadiness' gives conflicting results when run from different organizations?


Simeon MacMillen
 

I'm trying to install chaincode on a multi-host network (currently 2 orgs, each running on its own VPS server).  After packaging, installing, and approving the chaincode on each org's peer (each org currently has 1 peer), I run `checkcommitreadiness`.  Each time, it shows that the current org has approved the chaincode while the other org has not.

Example: (from OrgB):

peer lifecycle chaincode checkcommitreadiness --channelID scm1 --name scm --version 1 --sequence 1 --signature-policy 'OR('\''OrgBMSP.member'\'','\''OrgAMSP.member'\'')' --collections-config /home/user_b/Project/files/collections_config.json --output json
{
        "approvals": {
                "OrgAMSP": false,
                "OrgBMSP": true
        }
}


From OrgA:

peer lifecycle chaincode checkcommitreadiness --channelID scm1 --name scm --version 1 --sequence 1 --signature-policy 'OR('\''OrgAMSP.member'\'','\''OrgBMSP.member'\'')' --collections-config /home/user_a/Project/files/collections_config.json --output json
{
        "approvals": {
                "OrgAMSP": true,
                "OrgBMSP": false
        }
}

It would seem that the two organizations do not have visibility of each other, however the peer and orderer logs seem to show cross-visibility.

Has anyone else encountered this situation?  Do you have any ideas on what could lead to this result?


Logs and related information are available below:

Orderer Log (A): https://pastebin.com/vnZe5zKF
Orderer Log (B): https://pastebin.com/xGA35nbu
Peer Log (A): https://pastebin.com/WR3ugdSq
Peer Log (B): https://pastebin.com/zB2Up2iC
Stdout (A): https://pastebin.com/dDpjt2xn
Stdout (B): https://pastebin.com/iW1Fs78p


Regards,
Simeon MacMillen

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