Hyperledger fabric Hyperledger fabric 2.0：已提交状态（背书\策略\失败）

我试图按照以下步骤来试验HLF2.0链代码生命周期：

该网络有3个订购节点，每个节点有两个ORG和一个对等节点

但是在链码提交中，我得到了错误

committed with status (ENDORSEMENT_POLICY_FAILURE) at peer1.base.right:9051

configtx.yml

     Organizations:
    - &OrdererOrg
        Name: OrdererOrg
        ID: OrdererMSP
        MSPDir: crypto-config/ordererOrganizations/base.order/msp
        Policies:
            Readers:
                Type: Signature
                Rule: "OR('OrdererMSP.member')"
            Writers:
                Type: Signature
                Rule: "OR('OrdererMSP.member')"
            Admins:
                Type: Signature
                Rule: "OR('OrdererMSP.admin')"

    - &Org1
        Name: LeftOrgMSP
        ID: LeftOrgMSP
        MSPDir: crypto-config/peerOrganizations/base.left/msp
        Policies:
            Readers:
                Type: Signature
                Rule: "OR('LeftOrgMSP.admin', 'LeftOrgMSP.peer', 'LeftOrgMSP.client','LeftOrgMSP.member')"
            Writers:
                Type: Signature
                Rule: "OR('LeftOrgMSP.admin', 'LeftOrgMSP.client','LeftOrgMSP.peer','LeftOrgMSP.member')"
            Admins:
                Type: Signature
                Rule: "OR('LeftOrgMSP.admin','LeftOrgMSP.peer')"
            Endorsement:
                Type: Signature
                Rule: "OR('LeftOrgMSP.peer')"    
        AnchorPeers:
            - Host: peer1.base.left
              Port: 7051

    - &Org2
        Name: RightOrgMSP
        ID: RightOrgMSP
        MSPDir: crypto-config/peerOrganizations/base.right/msp
        Policies:
            Readers:
                Type: Signature
                Rule: "OR('RightOrgMSP.admin', 'RightOrgMSP.peer', 'RightOrgMSP.client','RightOrgMSP.member')"
            Writers:
                Type: Signature
                Rule: "OR('RightOrgMSP.admin','RightOrgMSP.peer', 'RightOrgMSP.client','RightOrgMSP.member')"
            Admins:
                Type: Signature
                Rule: "OR('RightOrgMSP.admin','RightOrgMSP.peer')"
            Endorsement:
                Type: Signature
                Rule: "OR('RightOrgMSP.peer')"     

        AnchorPeers:
            - Host: peer1.base.right
              Port: 9051            

Capabilities:
    Channel: &ChannelCapabilities
       V2_0: true
    Orderer: &OrdererCapabilities
        V2_0: true
    Application: &ApplicationCapabilities
       V2_0: true

Application: &ApplicationDefaults
    Organizations:
    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
        LifecycleEndorsement:
            Type: ImplicitMeta
            Rule: "MAJORITY Endorsement"
        Endorsement:
            Type: ImplicitMeta
            Rule: "MAJORITY Endorsement"   
        BlockValidation:
            Type: ImplicitMeta
            Rule: "ANY Writers"    


    Capabilities:
        <<: *ApplicationCapabilities

Orderer: &OrdererDefaults
    BatchTimeout: 2s
    BatchSize:
        MaxMessageCount: 10
        AbsoluteMaxBytes: 99 MB
        PreferredMaxBytes: 512 KB
    Organizations:
    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
        BlockValidation:
            Type: ImplicitMeta
            Rule: "ANY Writers"

Channel: &ChannelDefaults
    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
        BlockValidation:
            Type: ImplicitMeta
            Rule: "ANY Writers"


    Capabilities:
        <<: *ChannelCapabilities

Profiles:
    MainChannel:
        Consortium: BaseConsortium
        <<: *ChannelDefaults
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
                - *Org2
            Capabilities:
                <<: *ApplicationCapabilities

    Raft:
        <<: *ChannelDefaults
        Capabilities:
            <<: *ChannelCapabilities
        Orderer:
            <<: *OrdererDefaults
            OrdererType: etcdraft
            EtcdRaft:
                Consenters:
                - Host: orderer1.base.order
                  Port: 7050
                  ClientTLSCert: crypto-config/ordererOrganizations/base.order/orderers/orderer1.base.order/tls/server.crt
                  ServerTLSCert: crypto-config/ordererOrganizations/base.order/orderers/orderer1.base.order/tls/server.crt
                - Host: orderer2.base.order
                  Port: 8050
                  ClientTLSCert: crypto-config/ordererOrganizations/base.order/orderers/orderer2.base.order/tls/server.crt
                  ServerTLSCert: crypto-config/ordererOrganizations/base.order/orderers/orderer2.base.order/tls/server.crt
                - Host: orderer3.base.order
                  Port: 9050
                  ClientTLSCert: crypto-config/ordererOrganizations/base.order/orderers/orderer3.base.order/tls/server.crt
                  ServerTLSCert: crypto-config/ordererOrganizations/base.order/orderers/orderer3.base.order/tls/server.crt



            Addresses:
                - orderer1.base.order:7050
                - orderer2.base.order:8050
                - orderer3.base.order:9050

            Organizations:
            - *OrdererOrg
            Capabilities:
                <<: *OrdererCapabilities
        Application:
            <<: *ApplicationDefaults
            Organizations:
            - <<: *OrdererOrg
        Consortiums:
            BaseConsortium:
                Organizations:
                - *Org1
                - *Org2

链码批准

peer lifecycle chaincode approveformyorg  --channelID basechannel --name fabcar --version 1.0 --init-required --package-id fabcar_1:206a5ce87aefb8b9780b75451523c2aa3ef718ceebaaeae5082ae88ea259b305 --sequence 1 -o orderer1.base.order:7050  --tls --cafile $CA_PATH

链码提交命令

peer lifecycle chaincode commit -o orderer1.base.order:7050 --channelID basechannel --name fabcar --version 1.0 --sequence 1 --init-required --tls true --cafile $ORDER_CA_PATH  --peerAddresses peer1.base.right:9051 --tlsRootCertFiles $PATH_RIGHT --peerAddresses peer1.base.left:7051  --tlsRootCertFiles   $PATH_LEFT

---

我不知道为什么会出现这个错误，我正在考虑这样一个事实：所有的对等容器都已启动，MSP名称都是正确的

似乎缺少块验证策略

 BlockValidation:
        Type: ImplicitMeta
        Rule: "ANY Writers"

---

我正在考虑这样一个事实：所有的对等容器都已启动，MSP名称都是正确的

似乎缺少块验证策略

 BlockValidation:
        Type: ImplicitMeta
        Rule: "ANY Writers"

---

两天前我遇到了同样的问题，我刚刚解决了它。在提交链码之前，我的配置文件和操作没有任何问题，但我仍然得到了认可\u策略\u失败。检查调试日志后，我发现您应该同时将链码提交到足够多的背书节点，以获得足够多的签名以确保背书成功，我的fabric网络中有30多个组织，但一开始我只将链码提交到一个节点，这并不奇怪我会出现这个错误。

我两天前遇到了同样的问题，我刚刚解决了它。在提交链码之前，我的配置文件和操作没有任何问题，但我仍然得到了认可\u策略\u失败。检查调试日志后，我发现您应该同时将链码提交到足够多的背书节点，以获得足够多的签名以确保背书成功，我的fabric网络中有30多个组织，但一开始我只将链码提交到一个节点，我出现此错误并不奇怪。

您可以共享chaincode实例化命令以及完整的configtx.yaml文件吗？我正在使用HLF 2.0更新问题好的，您可以共享policy命令吗？在该命令中，您可以定义像and（'Org1.peer'）这样的策略。我没有指定策略它是默认的。您可以共享chaincode实例化命令和完整的configtx.yaml文件吗。我正在使用HLF 2.0更新问题好的，您可以共享策略命令吗，在这里您可以定义像and（'Org1.peer'）这样的策略。我没有指定策略它是默认的。您找到解决方案了吗？同样的事情也发生在我身上，你找到解决办法了吗？同样的事情也发生在我身上。