Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-78416

Failure in resume_query_from_non_existent_record.js in fcv upgrade downgrade suite

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • Repl 2023-07-10

      This is a new failure in fcv_upgrade_downgrade_replica_sets_jscore_passthrough suite, possibly related to the latest checkin for SERVER-77630. Failure is as follows:

      [js_test:resume_query_from_non_existent_record] 2023-06-23T23:18:14.595Z assert: command did not fail with any of the following codes [ 211 ] {
      [js_test:resume_query_from_non_existent_record]         "ok" : 0,
      [js_test:resume_query_from_non_existent_record]         "errmsg" : "Malformed resume token: the '_resumeAfter' object must contain exactly one field named '$recordId', of type NumberLong, BinData or jstNULL.",
      [js_test:resume_query_from_non_existent_record]         "code" : 2,
      [js_test:resume_query_from_non_existent_record]         "codeName" : "BadValue",
      [js_test:resume_query_from_non_existent_record]         "$clusterTime" : {
      [js_test:resume_query_from_non_existent_record]                 "clusterTime" : Timestamp(1687562294, 6),
      [js_test:resume_query_from_non_existent_record]                 "signature" : {
      [js_test:resume_query_from_non_existent_record]                         "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
      [js_test:resume_query_from_non_existent_record]                         "keyId" : NumberLong(0)
      [js_test:resume_query_from_non_existent_record]                 }
      [js_test:resume_query_from_non_existent_record]         },
      [js_test:resume_query_from_non_existent_record]         "operationTime" : Timestamp(1687562294, 6)
      [js_test:resume_query_from_non_existent_record] }
      [js_test:resume_query_from_non_existent_record] _getErrorWithCode@src/mongo/shell/utils.js:24:13
      [js_test:resume_query_from_non_existent_record] doassert@src/mongo/shell/assert.js:18:14
      [js_test:resume_query_from_non_existent_record] _assertCommandFailed@src/mongo/shell/assert.js:834:29
      [js_test:resume_query_from_non_existent_record] assert.commandFailedWithCode@src/mongo/shell/assert.js:882:16
      [js_test:resume_query_from_non_existent_record] testFindCmd@jstests/core/resume_query_from_non_existent_record.js:71:12
      [js_test:resume_query_from_non_existent_record] @jstests/core/resume_query_from_non_existent_record.js:137:1
      [js_test:resume_query_from_non_existent_record] @jstests/core/resume_query_from_non_existent_record.js:139:3

      This is the evergreen patch link: https://parsley.mongodb.com/resmoke/6f6fc2b407680975368ea85880ff7721/test/176b6cf6f6ba457b4d5f30fc486aa855?bookmarks=0,71&shareLine=0

            Assignee:
            jiawei.yang@mongodb.com Jiawei Yang
            Reporter:
            adi.zaimi@mongodb.com Adi Zaimi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: