Skip to content

Commit

Permalink
[FAB-12114] Upgrade doc note about enough peers
Browse files Browse the repository at this point in the history
Fix uprade doc note about having enough peers
upgrade to meet endorsement policy.

Change-Id: Ib4844b9c4919488f1d3aa1e30d67a9da583ac514
Signed-off-by: David Enyeart <enyeart@us.ibm.com>
  • Loading branch information
denyeart committed Sep 24, 2018
1 parent a5a3163 commit ce1cad6
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions docs/source/upgrading_your_network_tutorial.rst
Original file line number Diff line number Diff line change
Expand Up @@ -323,11 +323,12 @@ Verify peer upgrade completion
We’ve completed the upgrade for our first peer, but before we move on let’s check
to ensure the upgrade has been completed properly with a chaincode invoke.

.. note:: Before you attempt this, make sure you've upgraded enough peers from
enough organizations to satisfy your endorsement policy. Because the
endorsement policy for the chaincode in BYFN is ``"AND ('Org1MSP.peer','Org2MSP.peer')"``,
you'll need to have at least one peer from each org upgraded before
attempting to verify the upgrade.
.. note:: Before you attempt this, you may want to upgrade peers from
enough organizations to satisfy your endorsement policy.
Although, this is only mandatory if you are updating your chaincode
as part of the upgrade process. If you are not updating your chaincode
as part of the upgrade process, it is possible to get endorsements
from peers running at different Fabric versions.

Before we get into the CLI container and issue the invoke, make sure the CLI is
updated to the most current version by issuing:
Expand Down

0 comments on commit ce1cad6

Please sign in to comment.