validate_collections.js hook should tolerate KeyTooLong error response when forcing featureCompatibilityVersion

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.5.7
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • ALL
    • Hide
      python buildscripts/resmoke.py --executor=jstestfuzz_replication repro_server28501.js
      
      repro_server28501.js
      assert.commandWorked(db.adminCommand({setFeatureCompatibilityVersion: "3.2"}));
      assert.writeOK(db.getSiblingDB("admin").system.version.insert({version: "x".repeat(1025)}));
      
      Show
      python buildscripts/resmoke.py --executor=jstestfuzz_replication repro_server28501.js repro_server28501.js assert.commandWorked(db.adminCommand({setFeatureCompatibilityVersion: "3.2" })); assert.writeOK(db.getSiblingDB( "admin" ).system.version.insert({version: "x" .repeat(1025)}));
    • TIG 2017-05-08
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If running the "setFeatureCompatibilityVersion" command fails when TestData.forceValidationWithFeatureCompatibilityVersion is set, then we should bail out of validating any of the collections on the server. The KeyTooLong error response can only come from the "setFeatureCompatibilityVersion" command when the server is in featureCompatibilityVersion=3.2 since there isn't an already existing index on the "version" field.

            Assignee:
            Eddie Louie (Inactive)
            Reporter:
            Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: