Failure Scenario

1- Started the network with privatechannel_cc v1 chaincode installed
2- Did multiple transactions 
3- Ran a script to upgrade the privatechannel_cc v2 ( GOT THE ABOVE ERROR)
`COULD NOT ASSEMBLE TRANSACTION, ERR PROPOSAL RESPONSE WAS NOT SUCCESSFUL, ERROR CODE 500, MSG INSTANTIATION POLICY VIOLATION: SIGNATURE SET DIDNOT SATIFY POLICY`
4- The condition for step 3 is that the peer went down just before the chaincode upgrade and were out-of-sync. They were in the process of fetching all the previous blocks and the chaincode containers of V1 were down on both machines.

Checked the IDs (Hashes) of chaincodes installed on Peers of both Orgs and they are same.
Tried to instantiate instead of upgrade and it gives error as the chaincode is already instantiated.
Tried to query/invoke the chaincode and it gives the following error

"[channel org1channel] failed to get chaincode container info for privatechannel_cc:v1: could not get chaincode code: chaincode fingerprint mismatch: data mismatch" 

LOGS of the peer are attached in the file below.

peer chaincode upgrade -C org1channel -n privatechannel_cc -l golang -v v2 -c '{"Args":["init"]}' -P "OutOf(2,'org1MSP.member','org2MSP.member')" -o 192.168.171.32:7050 --tls --cafile /data/tls/ca.pem --clientauth --keyfile /data/tls/client-key.pem --certfile /data/tls/client.pem