[SERVER-49026] pseudo_commands.js can kill operation with opId '1234' mistakenly Created: 23/Jun/20  Updated: 29/Oct/23  Resolved: 23/Jun/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.4.1, 4.7.0

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Execution Team 2020-06-29
Participants:
Linked BF Score: 7

 Description   

The pseudo_commands.js test chooses opId '1234' to test proper authorization privileges. Unfortunately, the test can end up killing an internal thread by mistake causing an invariant in the server. A suitable fix for this could be to use the maximum possible opId (2^31 - 1).



 Comments   
Comment by Githook User [ 04/Aug/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-49026 Use the maximum opId to test authorization privilieges for killOp

(cherry picked from commit fc58564f8a211c7013c8e2324c5488417db42bd6)
Branch: v4.4
https://github.com/mongodb/mongo/commit/8aca7920701c09dca35207addb62e49be93312aa

Comment by Githook User [ 23/Jun/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-49026 Use the maximum opId to test authorization privilieges for killOp
Branch: master
https://github.com/mongodb/mongo/commit/fc58564f8a211c7013c8e2324c5488417db42bd6

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