[SERVER-40452] Attach uuid to createCollection oplog entry in idempotency tests Created: 02/Apr/19  Updated: 29/Oct/23  Resolved: 21/May/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.12

Type: Bug Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: test-fix
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2019-05-20, Execution Team 2019-06-03
Participants:

 Description   

This is a test-only fix.
SERVER-39514 blacklisted a bunch of idempotency unit tests because the change exposed a problem: Those tests didn't put UUIDs to the 'ui' fields of oplog entries, causing createCollectionForApplyOps to bypass this check ans the code path and tried to create another collection with the same UUID.

Before SERVER-39514, on creating a new collection, UUIDCatalog unconfidently deregister the UUID if it already exists. SERVER-39514 added an assertion that the UUID should never be there, thus catching this bug.

The fix would be to always attach uuid to these oplog entries.
The affected tests are:
idempotency_test
sync_tail_test
rs_rollback_test

`git grep SERVER-40452` for all the places.



 Comments   
Comment by Githook User [ 21/May/19 ]

Author:

{'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}

Message: SERVER-40452 Attach uuid to createCollection oplog entry in idempotency tests
Branch: master
https://github.com/mongodb/mongo/commit/62906f2fae85fc734e52e7190799072717374cbb

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