[SERVER-76697] Correctly check for failure in mongos setAuditConfig Created: 28/Apr/23 Updated: 02/May/23 Resolved: 28/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gabriel Marks | Assignee: | Gabriel Marks |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Backport Requested: |
v7.0
|
||||
| Participants: | |||||
| Description |
|
Note that this is actually fixed in master, but not in 7.0. We forward setAuditConfig to the config server with runCommand, but we only check the result of runCommand and not the commandStatus of the response, meaning we incorrectly succeed when the config server command fails. |