[SERVER-31539] applyOps must ensure correct db for UUID Created: 12/Oct/17  Updated: 30/Oct/23  Resolved: 23/Oct/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

db.runCommand({ applyOps: (uuid => ["test", "test2"].map(db => { return { op: "c", ns: db + ".$cmd", ui: uuid, o: {create: "foo"}}}))(UUID()) })

Sprint: Storage 2017-10-23, Storage 2017-11-13
Participants:

 Description   

Running the applyOps command with a known UUID but wrong database for that UUID can crash the server.



 Comments   
Comment by Githook User [ 23/Oct/17 ]

Author:

{'email': 'geert@mongodb.com', 'name': 'Geert Bosch', 'username': 'GeertBosch'}

Message: SERVER-31539 applyOps create fails if UUID already exists in different DB
Branch: master
https://github.com/mongodb/mongo/commit/9af189775db7b17b265d18a04ca0dc314792a4c5

Comment by Ian Whalen (Inactive) [ 23/Oct/17 ]

Bumping to RC2 just to avoid blocking the RC1 release on this for now.

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