-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.4.25, 7.0.2, 5.0.22, 6.0.11
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
v8.0, v7.0, v6.0, v5.0
-
(copied to CRM)
[direct: mongos] test> db.getSiblingDB("admin").fsyncUnlock() MongoServerError[Unauthorized]: not authorized on admin to execute command { fsyncUnlock: 1, lsid: { id: UUID("015b53df-9147-4bff-80bd-197438e71aaa") }, $clusterTime: { clusterTime: Timestamp(1713328347, 1), signature: { hash: BinData(0, 5D83869EB170A3A0988F51E11062C69D01B2944D), keyId: 7358683174655754254 } }, $db: "admin" }
We encounter the above permission issue when executing with the root role for the fsyncunlock command.
The fsync unlock cmd has the ActionType::fsyncUnlock, but we do not have a corresponding role in the builtin_roles.cpp (here)
- is caused by
-
SERVER-78150 Implement the mongos fsyncUnlock command
- Closed
-
SERVER-78151 Add fsyncLock status to the mongos currentOp command
- Closed
- is duplicated by
-
SERVER-90566 Permissions to fsyncLock are not the same as to fsyncUnlock
- Closed
- is related to
-
SERVER-97013 Adjust 8.0.4 Backports
- Closed