Peer Does Not Connect to The Correct Chaincode Container After Upgrade on the Oracle Blockchain Platform(OBP)
(Doc ID 2744197.1)
Last updated on FEBRUARY 01, 2024
Applies to:
Blockchain Platform Cloud Service - Version N/A to N/AInformation in this document applies to any platform.
Symptoms
On OBP, The user had a new issue with the "diamonds" chain code deployed on the "<Channelname>" channel. user upgraded several times to new versions but it does not look like the peer is picking up the correct one. The newest chain code version instantiated on that channel is "diamonds:2.4.1" (patch), however, those changes seem not to be present on it.
The correct incoming input via the OBP dashboard transaction tab, so should something related to the chain code itself.
To enforce what said above, restarted the peers and besides the expected connection error for the chain code container, found the following log in it:
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |