[SERVER-55831] ensure cause is clear when jstests user_defined_roles_on_secondaries.js fails Created: 06/Apr/21  Updated: 29/Oct/23  Resolved: 07/Apr/21

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Sergey Galtsev (Inactive) Assignee: Sergey Galtsev (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Security 2021-04-19
Participants:
Linked BF Score: 147

 Description   

in BF-20634 we have an unclear cause of failure. It could be one of:

  • dropRole could have failed, and since we are not checking result we can't tell it didn't
  • call could have returned before replication completed, and since we are not checking primary first, we can't tell it's not the case

I am making an attempt to reproduce an issue on windows/debug, so far without success.

After discussion with xuerui.fa we decided following needs to be done:

  • check that dropRole succeeds
  • check that after dropRole succeeds, the role has indeed disappeared from primary before checking all other nodes

This will not address the root cause, but will help eliminate possibilities



 Comments   
Comment by Githook User [ 07/Apr/21 ]

Author:

{'name': 'Sergey Galtsev', 'email': 'sergey.galtsev@mongodb.com', 'username': 'brushless-glitch'}

Message: SERVER-55831 additional checks on user_defined_roles_on_secondaries
Branch: master
https://github.com/mongodb/mongo/commit/6cf1dbd9e91e17aee4de4a4dcceffa559a53ae66

Comment by Sergey Galtsev (Inactive) [ 06/Apr/21 ]

http://mongodbcr.appspot.com/755040004

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