It appears you are attempting to re-approve chaincode sequence #1. If your peers don't have the original approval private data anymore, you are not able to 'edit' your existing approval record. Your only option would be to increment the chaincode to sequence #2 and gather new approvals for sequence #2.
Dave Enyeart
"Sebastian Meyer zu Borgsen" ---10/27/2021 07:56:09 AM---Hi, We experience a problem that we cannot approve a newer chaincode version for our org.
From: "Sebastian Meyer zu Borgsen" <sebastian.meyer-zu-borgsen@...> To: <fabric@...> Date: 10/27/2021 07:56 AM Subject: [EXTERNAL] [Hyperledger Fabric] ApproveChaincodeDefinitionForMyOrg fails with private data missing Sent by: fabric@...
Hi, We experience a problem that we cannot approve a newer chaincode version for our org. Due to a reinstall of the org’s peers we have no access to the private data of the previous approval. ApproveChaincodeDefinitionForMyOrg produces ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Hi,
We experience a problem that we cannot approve a newer chaincode version for our org. Due to a reinstall of the org’s peers we have no access to the private data of the previous approval. ApproveChaincodeDefinitionForMyOrg produces an error with the following content:
Error: proposal failed with status: 500 - failed to invoke backing implementation of 'ApproveChaincodeDefinitionForMyOrg': could not serialize chaincode parameters to state: could not deserialize metadata for namespace namespaces/CC#1: could not query metadata for namespace namespaces/CC#1: GET_STATE failed: transaction ID: abcd1234 private data matching public hash version is not available. Public hash version = {BlockNum: 1337, TxNum: 0}, Private data version = <nil>
What is the reason for fabric requesting the private data from the old approval? Is there an option to approve without the old private data?
"Sebastian Meyer zu Borgsen" ---10/27/2021 07:56:09 AM---Hi, We experience a problem that we cannot approve a newer chaincode version for our org.