[SERVER-11584] RenameCollection seems not to be audited in a sharded cluster Created: 05/Nov/13  Updated: 10/Dec/14  Resolved: 06/Nov/13

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

Type: Bug Priority: Major - P3
Reporter: bard.bloom@10gen.com Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

renameCollection doesn't seem to produce audit log records in sharded clusters. (It does produce them in our standalone and 3-node repl set configurations).



 Comments   
Comment by Matt Dannenberg [ 06/Nov/13 ]

the collection being renamed was sharded
but a sharded collection cannot be renamed
so it was not renamed
hence no auditlog message

Generated at Thu Feb 08 03:26:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.