Uploaded image for project: 'Fabric'
  1. Fabric
  2. FAB-16857

fabric-test-daily-pte-master job: Consistent failure to send install Proposal in 3 of the PTE test cases

    XMLWordPrintable

Details

    • (Please add steps to reproduce)

    Description

      Build Logs: fabric-test-daily-pte-master job: Failed to send install Proposal in 4 of the PTE test cases, same error is observed in below test cases

      Error was consistent and first observed on 12 oct 2019.

       

      Note: In some other testcases, FAB-16866, it appears that subsequent instantiations and invokes succeeded anyways after the install errors were seen.

       

      Branch: Master

      Platform: x86_64

      Error Snippet:

      /+ echo './pte_driver.sh CITest/FAB-6813-4i/preconfig/channels/runCases-chan-join-TLS.txt'
      + ./pte_driver.sh CITest/FAB-6813-4i/preconfig/channels/runCases-chan-join-TLS.txt
      + sleep 60s
      + set +exo pipefail
      #x1B[31merror#x1B[39m: [2019-10-15T02:10:07.685Z PTE 0 main]: [chaincodeInstall] org(org2): install proposal was bad
      #x1B[31merror#x1B[39m: [2019-10-15T02:10:07.686Z PTE 0 main]: [chaincodeInstall] org(org2): install proposal was bad
      #x1B[31merror#x1B[39m: [2019-10-15T02:10:07.686Z PTE 0 main]: [chaincodeInstall] Failed to install chaincode in (PeerOrg2) due to error:  message=[chaincodeInstall] Failed to send install Proposal in (%s) or receive valid response. Response null or status is not 200. exiting..., stack=Error: [chaincodeInstall] Failed to send install Proposal in (%s) or receive valid response. Response null or status is not 200. exiting...
          at /w/workspace/fabric-test-daily-pte-master-x86_64/gopath/src/github.com/hyperledger/fabric-test/tools/PTE/pte-main.js:684:27
          at <anonymous>
      #x1B[31merror#x1B[39m: [2019-10-15T02:10:07.754Z PTE 0 main]: [chaincodeInstall] org(org1): install proposal was bad
      #x1B[31merror#x1B[39m: [2019-10-15T02:10:07.755Z PTE 0 main]: [chaincodeInstall] org(org1): install proposal was bad
      #x1B[31merror#x1B[39m: [2019-10-15T02:10:07.755Z PTE 0 main]: [chaincodeInstall] Failed to install chaincode in (PeerOrg1) due to error:  message=[chaincodeInstall] Failed to send install Proposal in (%s) or receive valid response. Response null or status is not 200. exiting..., stack=Error: [chaincodeInstall] Failed to send install Proposal in (%s) or receive valid response. Response null or status is not 200. exiting...
          at /w/workspace/fabric-test-daily-pte-master-x86_64/gopath/src/github.com/hyperledger/fabric-test/tools/PTE/pte-main.js:684:27
          at <anonymous>/ code placeholder
      

       Build Logs: 

      /[32minfo: [2019-10-15T03:26:17.813Z PTE 0 main]: stdout: info: [2019-10-15T03:26:17.812Z PTE 0 exec]: [Nid:chan:org:id=0:testorgschannel1:org1:0 invoke_query_simple] query[10000] result[0]: Error: make sure the chaincode sample_js_ch1 has been successfully defined on channel testorgschannel1 and try again: chaincode sample_js_ch1 not found
      
      info: [2019-10-15T03:26:17.813Z PTE 0 main]: stdout: info: [2019-10-15T03:26:17.813Z PTE 0 exec]: [Nid:chan:org:id=0:testorgschannel1:org1:0 isExecDone] invokes(Query) sent: number=10000, elapsed time= 315039
      
      info: [2019-10-15T03:26:17.813Z PTE 0 main]: stdout: info: [2019-10-15T03:26:17.813Z PTE 0 exec]: [Nid:chan:org:id=0:testorgschannel1:org1:0 invoke_query_simple] query result[0]: Error: make sure the chaincode sample_js_ch1 has been successfully defined on channel testorgschannel1 and try again: chaincode sample_js_ch1 not found
      / code placeholder
      

      https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-test-daily-pte-master-x86_64/372/PTE_Test_Logs

      https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-pte-master-x86_64/372/testReport/systest_pte/

      Attachments

        Issue Links

          Activity

            People

              bharadwajambati1 Bharadwaj Ambati
              vijaypunugubati VIJAY BABU PUNUGUBATI
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: