Perform manual testing on evaluate when non-gateway peers go down cleanly

[davidkel]

This is going to be more tricky to test, because if the chaos engine runs in evaluate mode only and the scenarios always leave the gateway peer up, then the gateway peer is always going to be chosen for the evaluate, the only slight change is that it may try the other peer in the org first if the 2 have the same block heights, but no guarantee (Would need to confirm with Andy but I suspect that the gateway peer will always be the first peer to try if the block heights are identical to cut down on any unnecessary network traffic)

[davidkel]

We may be able to test this by not installing chaincode on the gateway peer, but we can use unsetting of the gossip external endpoint as this doesn't work with the gateway

[davidkel]

We may need to test 3 peers in the same org ?

[davidkel]

tested by

• installing chaincode on peer0 of each org
• gateway peer was peer1.org1
• stopped peer peer1.org2, peer1.org3 so that chaos engine won't include these when attempting any stop or restart

Issues raised

• Bringing down peers during evaluate returns unexpected errors to client hyperledger/fabric-gateway#276 (when no error was expected)
• Recommendation for evaluate error message hyperledger/fabric-gateway#282 (when failures are expected)

[davidkel]

Scenarios used

StopRestartOrg2
StopRestartOrg3
StopRestartOrg12Peer
StopRestartOrg13Peer
StopRestartOrg23Peer
StopRestartOrg1Peer
StopRestartOrg2Peer
StopRestartOrg3Peer

Can't stop all peers except gateway because gateway cannot endorse so this will fail, and we can't stop a peer in all orgs because org2 and org3 only have 1 peer and we can't stop the non gateway peer in org 1