[SERVER-25064] Auth regression in nightlies on Windows and Solaris Created: 14/Jul/16 Updated: 19/Jul/16 Resolved: 17/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 17 (07/15/16), Sharding 18 (08/05/16) |
| Participants: |
| Description |
|
Beginning a few days ago, the mongo shell cannot authenticate to mongos during the C Driver's Evergreen startup. For an example task failure, see https://evergreen.mongodb.com/task/mongo_c_driver_windows_64_vs2010_integration_test_latest_sharded_7e0105c26ef1b295739465afc8d4dac6218f0ea5_16_07_14_17_31_13. It logs:
|
| Comments |
| Comment by Githook User [ 17/Jul/16 ] | |||
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Also extend the auth tests to validate that both variants work. | |||
| Comment by Spencer Jackson [ 14/Jul/16 ] | |||
|
This stack trace from that log makes me suspect the problem occurs when trying to create the user:
That error, gets emitted from ShardingCatalogClientImpl::runUserManagementWriteCommand if `!writeConcern.validForConfigServers()`. 7c67f3a6fd52ea4933c23ce89f1cc5da62628ec4, in the range identified by max.hirschhorn, seems to have changed the behavior of validForConfigServers. kaloian.manassiev, can you take a look at this? Does it make sense that these errors should be observed, and do you have any idea why they might only be manifesting on specific platforms? | |||
| Comment by Max Hirschhorn [ 14/Jul/16 ] | |||
|
Based on the last success and the first failure, the change in behavior of the server occurred between 3.3.9-58-g4efc4c9 and 3.3.9-199-g7991001. |