[SERVER-22584] Make sure IncompatibleCatalogManager errors fully propagate wherever thrown Created: 11/Feb/16  Updated: 25/Jan/17  Resolved: 17/Feb/16

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: code-only, csrsupgrade
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 10 (02/19/16)
Participants:

 Comments   
Comment by Githook User [ 17/Feb/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-22584 Make sure authentication code doesn't swallow IncompatibleCatalogManager errors
Branch: v3.2
https://github.com/mongodb/mongo/commit/ef8d198e99eaeadc1f1441661aba052b44f82258

Comment by Githook User [ 17/Feb/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-22584 Make sure SyncClusterConnection never swallows IncompatibleCatalogManager errors
Branch: v3.2
https://github.com/mongodb/mongo/commit/fcde5c308ef3856c5be47769cec975f9a0e147df

Generated at Thu Feb 08 04:00:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.