aws-samples / non-profit-blockchain

Builds a blockchain network and application to track donations to non-profit organizations, using Amazon Managed Blockchain
Apache License 2.0
373 stars 288 forks source link

Can not update channel with the new configuration (includes 3 orgs in 1 channel) #30

Closed tranquangvu closed 5 years ago

tranquangvu commented 5 years ago

I have completed all parts in your tutorials. Everything works fine.

After that, i try to add 3rd member follow steps in Part 5. But i got an error in Step 11: Account A updates the channel with the new configuration like below:

Error: got unexpected status: BAD_REQUEST -- error authorizing update: error validating DeltaSet: policy for [Group] /Channel/Application not satisfied: Failed to reach implicit threshold of 2 sub-policies, required 1 remaining

Screen Shot 2019-06-27 at 4 53 06 PM

This is my config in ~/configtx.yaml file

# Copyright 2018 Amazon.com, Inc. or its affiliates. All Rights Reserved.
# 
# Licensed under the Apache License, Version 2.0 (the "License").
# You may not use this file except in compliance with the License.
# A copy of the License is located at
# 
#     http://www.apache.org/licenses/LICENSE-2.0
# 
# or in the "license" file accompanying this file. This file is distributed 
# on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either 
# express or implied. See the License for the specific language governing 
# permissions and limitations under the License.

################################################################################
#
#   Section: Organizations
#
#   - This section defines the different organizational identities which will
#   be referenced later in the configuration.
#
################################################################################
Organizations:
    - &Org1
        Name: 

        # ID to load the MSP definition as
        ID: 

        MSPDir: /opt/home/admin-msp

        AnchorPeers:
            # AnchorPeers defines the location of peers which can be used
            # for cross org gossip communication.  Note, this value is only
            # encoded in the genesis block in the Application section context
            - Host:
              Port:
    - &Org2
        Name: 
        ID: 
        MSPDir: 
        AnchorPeers:
            - Host:
              Port:

    - &Org3
        Name: 
        ID: 
        MSPDir: 
        AnchorPeers:
            - Host:
              Port:

################################################################################
#
#   SECTION: Application
#
#   - This section defines the values to encode into a config transaction or
#   genesis block for application related parameters
#
################################################################################
Application: &ApplicationDefaults

    # Organizations is the list of orgs which are defined as participants on
    # the application side of the network
    Organizations:

################################################################################
#
#   Profile
#
#   - Different configuration profiles may be encoded here to be specified
#   as parameters to the configtxgen tool
#
################################################################################
Profiles:
    OneOrgChannel:
        Consortium: AWSSystemConsortium
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
    TwoOrgChannel:
        Consortium: AWSSystemConsortium
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
                - *Org2
    ThreeOrgChannel:
        Consortium: AWSSystemConsortium
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
                - *Org2
                - *Org3

What should i do to fix this problem?

MCLDG-zz commented 5 years ago

The error indicates that both of the members must sign the channel update config file before you update the channel config.

On Thu, 27 Jun 2019, 17:54 tranquangvu, notifications@github.com wrote:

I have completed all parts in your tutorials. Everything work fine.

After that, i try to add 3rd member follow steps in Part 5. But i got an error in step 11: Step 11: Account A updates the channel with the new configuration like below:

[image: Screen Shot 2019-06-27 at 4 53 06 PM] https://user-images.githubusercontent.com/6037861/60256614-14d20700-98fc-11e9-8c49-c66387eb8a3e.png

This is my config in ~/configtx.yaml file

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/aws-samples/non-profit-blockchain/issues/30?email_source=notifications&email_token=AC6QOGT5XCZQF6AZ3EAQ52DP4SE5HA5CNFSM4H32H7U2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G4A5E7Q, or mute the thread https://github.com/notifications/unsubscribe-auth/AC6QOGVWRGV7O2YBL2LY42LP4SE5HANCNFSM4H32H7UQ .