title: peer chaincode instantiate - instantiation policy violation: signature set did not satisfy policy
body: <p>I am using Hyperledger Fabric v1.2.  I am trying to instantiate chaincode on a single peer and I just have one org and an orderer org specified on my configtx.yaml for my network. I haven't made any changes to the ACL in my configtx.yaml so its what is set to by default.</p>
  
  <p>When I run this command:</p>
  
  <pre><code>./peer chaincode instantiate -o orderer1.example.com:7050  -C devchannel -n jmo01 -v 1.0 -c '{"Args":["init","a", "100", "b","200"]}' -P "OR ('SampleOrgMSP.member')" --cafile /etc/hyperledger/fabric/msp/peer1/msp/cacerts/cert.pem
  </code></pre>
  
  <p>It throws the following error in the peer:</p>
  
  <pre><code>Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg instantiation policy violation: signature set did not satisfy policy
  </code></pre>
  
  <p>Profiles in configtx.yaml:</p>
  
  <pre><code>Profiles:
      # SampleDevModeKafka defines a configuration that differs from the
      # SampleDevModeSolo one only in that it uses the Kafka-based orderer.
      SampleOrgGenesis:
          &lt;&lt;: *ChannelDefaults
          Orderer:
              &lt;&lt;: *OrdererDefaults
              OrdererType: kafka
              Organizations:
                  - &lt;&lt;: *SampleOrg
                    Policies:
                        &lt;&lt;: *SampleOrgPolicies
                        Admins:
                            Type: Signature
                            Rule: "OR('SampleOrgMSP.member')"
          Consortiums:
              SampleConsortium:
                  Organizations:
                      - &lt;&lt;: *SampleOrg
                        Policies:
                            &lt;&lt;: *SampleOrgPolicies
                            Admins:
                                Type: Signature
                                Rule: "OR('SampleOrgMSP.member')"
  
      MyChannel:
          Consortium: SampleConsortium
          Application:
              &lt;&lt;: *ApplicationDefaults
              Organizations:
                  - *SampleOrg
  </code></pre>
  
  <p>Organizations section at the top of configtx.yaml:</p>
  
  <pre><code>Organizations:
      - &amp;SampleOrdererOrg
          Name: SampleOrdererOrg
          ID: SampleOrdererOrgMSP
          MSPDir: /etc/hyperledger/msp/orderer1/msp
          Policies:
              Readers:
                  Type: Signature
                  Rule: "OR('SampleOrdererOrgMSP.member')"
              Writers:
                  Type: Signature
                  Rule: "OR('SampleOrdererOrgMSP.member')"
              Admins:
                  Type: Signature
                  Rule: "OR('SampleOrdererOrgMSP.admin')"
              BlockValidation:
                  Type: Signature
                  Rule: "OR('SampleOrdererOrgMSP.member')"
      - &amp;SampleOrg
          Name: SampleOrgMSP
          ID: SampleOrgMSP
  
          # MSPDir is the filesystem path which contains the MSP configuration.
          MSPDir: /etc/hyperledger/org/msp
          Policies: &amp;SampleOrgPolicies
              Readers:
                  Type: Signature
                  Rule: "OR('SampleOrgMSP.member')"
              Writers:
                  Type: Signature
                  Rule: "OR('SampleOrgMSP.member')"
              Admins:
                  Type: Signature
                  Rule: "OR('SampleOrgMSP.admin')"
          AnchorPeers:
              - Host: peer1.example.com
                Port: 7051
              - Host: peer2.example.com
                Port: 7051
              - Host: peer3.example.com
                Port: 7051
  </code></pre>
  
  <p>I'm thinking it has something to do with how I'm making the instantiation command and maybe I don't have the policy correctly set.  One of the policies is requiring a certain type of org user to complete the instantiation but I'm not sure which one it is where its member or admin and then what org msp should I be specifying.</p>