[SERVER-6495] Authing a RO user against rs with no primary doesn't work Created: 17/Jul/12  Updated: 10/Dec/14  Resolved: 13/Mar/14

Status: Closed
Project: Core Server
Component/s: Security, Sharding
Affects Version/s: 2.0.6, 2.1.2, 2.2.0-rc0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kristina Chodorow (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File out     File ro.js    
Issue Links:
Duplicate
duplicates SERVER-6665 authentication for a replica set requ... Closed
Operating System: ALL
Participants:

 Description   

ro.js - reproduces
out - output of test run



 Comments   
Comment by auto [ 02/Apr/13 ]

Author:

{u'date': u'2013-03-15T18:46:45Z', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: SERVER-6972 SERVER-6495 Use isMaster instead of replSetGetStatus for monitoring the health of a replica set
Branch: master
https://github.com/mongodb/mongo/commit/2d0f6cc207ac4574ead4bb4728bfef1e22229b67

Comment by Spencer Brody (Inactive) [ 18/Jul/12 ]

Reproduced both in 2.2-rc0 and in 2.0.6.

Comment by Andy Schwerin [ 18/Jul/12 ]

If not, add a comment to that affect, and drop the fix version so we can re-triage, later.

Comment by Spencer Brody (Inactive) [ 18/Jul/12 ]

Is this a regression from 2.0.6?

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