[SERVER-28501] validate_collections.js hook should tolerate KeyTooLong error response when forcing featureCompatibilityVersion Created: 25/Mar/17  Updated: 06/Dec/17  Resolved: 19/Apr/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.5.7

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Eddie Louie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

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)}));

Sprint: TIG 2017-05-08
Participants:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Githook User [ 19/Apr/17 ]

Author:

{u'username': u'elouie99', u'name': u'Eddie Louie', u'email': u'eddie.louie@mongodb.com'}

Message: SERVER-28501 validate_collections.js hook should tolerate KeyTooLong error response when forcing featureCompatibilityVersion
Branch: master
https://github.com/mongodb/mongo/commit/41d5d369508592a2c1ebaaaac48fe2b3680e0615

Generated at Thu Feb 08 04:18:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.